When service instances have changing network locations, clients can query a service registry instead of relying on fixed addresses. The client selects an available instance and sends the request directly to it. section 8.2.5
The client-side flow has three responsibilities:
- Retrieve available service instances from the registry; optionally cache the list. section 8.2.5
- Choose an instance using a load-balancing algorithm, such as round-robin or random selection. section 8.2.5
- Send the request to the selected instance. Netflix Eureka and Ribbon, and Spring Cloud integrations, support application-level discovery. section 8.2.5
Figure 8.10 The service registry keeps track of the service instances. Clients query the service registry to find network locations of available service instances.
Shows how clients query a registry for available service instances’ network locations. section 8.2.5
