GitHub user funky-eyes added a comment to the discussion: Discussion of seata-server and proxy compatibility programs
是的，你说的这种也是一种集群方案，可以用gossip之类的协议处理，或者社区提供一个支持seata协议的7层网关，避免连接级别这种粗粒度的负载均衡。但是这些方案都太重了。目前个人倾斜复用已有的raft集群模式，自带集群信息，通过tm，rm的registry request请求后，响应集群的response或者复用目前的http方式的集群列表获取，以便于建立真正的连接，绕过代理 Yes, the kind of thing you are talking about is also a clustering solution, which can be handled with protocols like gossip, or the community can provide a layer 7 gateway that supports the seata protocol to avoid such coarse-grained load balancing at the connection level. But all these solutions are too heavy. Currently, I'm leaning towards reusing the existing raft cluster model, which comes with cluster information, and responds to the cluster response after a registry request via tm, rm, or reusing the current http method of obtaining the cluster list, so as to make it easier to establish a real connection, bypassing proxies. GitHub link: https://github.com/apache/incubator-seata/discussions/6279#discussioncomment-8203312 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
