GitHub user YoWuwuuuw added a comment to the discussion: Add multicast support to registery module
I think the solution for service discovery based on multicast is a 'plus' of the file-based solution Enhancement of multicast: 1. Simplified configuration: There is no need to manually write the address of server cluster or single instance into the configuration file, only the address of Multicast group can be specified uniformly 2. Dynamism and flexibility: The online and offline of TC instances can be automatically perceived by the Seata client, and the client can dynamically adjust the TC list to optimize its connection allocation with available TC instances (load balancing) 3. Automated testing: Multicast In the automated testing environment, TC instances can be dynamically started and stopped, Seata The client can automatically discover TC instances without modifying the configuration file Shortcomings of multicast: 1. Reliability: It relies on the UDP protocol and needs to use a retry mechanism to mitigate packet loss, but it cannot fully guarantee message reliability. 2. Security: There is no encryption and authentication mechanism provided by the registration center 3. Network restrictions: can only be used within the LAN Based on these characteristics, I think the implementation of multicast is more convenient and easy to use for local testing, distributed deployment, and small applications than file-based service discovery GitHub link: https://github.com/apache/incubator-seata/discussions/7195#discussioncomment-12437871 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
