April 2018
Intermediate to advanced
432 pages
10h 38m
English
The Eureka Server caches responses by default. The cache is invalidated every 30 seconds. It can be easily checked by calling the HTTP API endpoint /eureka/apps. If you call it just after the registration of the client application, you will figure out that it is still not returned in the response. Try again after 30 seconds, and you will see that the new instance appears. The response cache timeout may be overridden with the responseCacheUpdateIntervalMs property. Interestingly, there is no cache while displaying a list of registered instances using the Eureka dashboard. In contrast to the REST API, it bypasses the response cache:
eureka: server: responseCacheUpdateIntervalMs: 3000
We should remember that the Eureka registry ...