This article walks through the Eureka dashboard’s System Status section, explains the meaning of each displayed metric, describes how the self‑preservation mode works and how to enable or disable it, and reviews cluster and instance information shown in a local Eureka cluster.
This article explains the architecture and core mechanisms of Eureka, a service registry used in Spring Cloud micro‑service environments, covering server components such as Lease and caching, client registration and discovery processes, self‑preservation mode, consistency trade‑offs, and comparisons with other discovery solutions.
This article explains Eureka's role as a Spring Cloud service registry, detailing its server and client components, registration and renewal processes, self‑preservation mechanism, clustering principles, and the complete workflow that enables reliable microservice discovery and high availability.
This article compares Netflix’s Eureka and Apache Zookeeper as service registration solutions, explaining their underlying AP and CP designs, how Eureka’s peer‑to‑peer architecture and self‑preservation mode ensure high availability, and why AP‑oriented registries may be preferable for typical microservice environments.
This article explains Eureka's normal workflow, how it registers services, replicates data, and maintains local caches, and details its fallback mechanisms, unavailable server handling, full‑outage resilience, and self‑preservation feature to keep microservice discovery reliable.
