Load balancing and high availability architecture for TCP access

1. Architecture diagram

1. The client requests the getTcpIP interface of web-server to obtain the list of available tcp service IPs, which can achieve load balancing and horizontal expansion
2. The web-server and tcp server keep heartbeat, and remove down services to ensure high availability.
3. Take the initiative to get the getStatus through the web-server instead of the report of the tcp server, which reflects that the service architecture cannot rely on reverse coupling; because the web-server is a subsystem, the main system should not depend on the derived subordinate system. Similarly, in the CDN architecture, the source cannot push the source file to the mirror, because normally the mirror depends on the source. If the source is dependent on the mirror, then the mistake of reverse dependency coupling is committed.

Two, reference

https://blog.csdn.net/aa1358075776/article/details/97779277