Micro-service architecture:
the basic process:
when each service starts, will be registering their information to consulClient, consulClient registration information submitted to the consulServer, consulServer to submit information to consulLeader (also consulServer), consulLeader to copy their data to other consulServer, service registration is complete! ! !
Issuing a request for the APP gatewayX-server, the request first to nginx, nginx gatewayX-server selecting a server for processing the request
gatewayX-server to access the particular logical myserviceA-server via myserviceA-client.jar
Firstly consulServer pull myserviceA-server on the server is available, the service found to be complete! ! !
Wherein selecting a server to be accessed in accordance with the load balancing policy
process accessible to timeout fault-tolerant through the fuse
gatewayX-server to access the particular logical myserviceB-server via myserviceB-client.jar with 3
: If just the front so the previous processes or processes such as edges and myserviceB-server basis to invoke myserviceA-server, the entire image above myserviceA-client.jar myserviceB-server may be removed, because gatewayX-server has been introduced myserviceA-client .jar.
If it is not on top of the process, but simply myserviceB-server to be accessed myserviceA-server, you need to introduce myserviceA-client.jar.
Note: For service discovery purposes, consulServer will pass gossip protocol server data broadcast to various local consul agent (usually consulClient), so we do not need a local cache, when the service is invoked server list changes, we will immediately broadcast to consulClient.
Original link: https://blog.csdn.net/xiangxizhishi/article/details/79434775