July 2017
Intermediate to advanced
414 pages
11h 18m
English
In the previous example, there was only one Eureka Server in the standalone mode. This is not good enough for a real production system.
The Eureka Client connects to the server, fetches registry information, and stores it locally in a cache. The client always works with this local cache. The Eureka Client checks the server periodically for any state changes. In case of a state change, it downloads the changes from the server and updates the cache. If the Eureka Server is not reachable, then the Eureka Client can still work with the last known state of the servers based on the data available in the client cache. However, this could lead to stale state issues quickly.
This section will explore high availability ...
Read now
Unlock full access