At this stage, we should emphasize one important thing, the zoning mechanism is realized only on the client side. This means that the service discovery instance is not assigned to any zone. So the preceding diagram may be slightly confusing, but it indicates which Eureka is the default service discovery for all client applications and gateways registered in the specific zone. Our purpose is to check out the mechanisms in the high availability mode, but we may as well build it only with a single discovery server. The following diagram illustrates a similar situation as the previous diagram, except that it assumes the existence of only a single discovery server for all of the applications:
Zones with a standalone server
Get Mastering Spring Cloud now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
