Understanding Spring Cloud Core Components: Eureka, Ribbon, Feign, Hystrix, and Zuul

Previously I have been studying Spring Cloud and microservice architecture; this article summarizes the main components of Spring Cloud in detail.

Spring Cloud Core Component: Eureka

Eureka Server acts as a service registry and supports high‑availability deployment. In cluster mode, if a node fails, Eureka enters self‑protection mode to continue providing discovery and registration until the node recovers.

Eureka Client handles service registration and discovery. Clients register themselves with the server and send periodic heartbeats to renew their lease, while also caching the registry locally and refreshing it regularly.

Eureka Details

A. Service Registration – Service providers send a REST request to the Eureka Server on startup, which stores metadata in a two‑level map (service name → instance name).

B. Service Synchronization – When multiple Eureka servers form a cluster, each server forwards registration requests to its peers, ensuring that all registries have consistent service information.

C. Service Renewal – After registration, providers maintain a heartbeat to tell the server they are alive, preventing automatic removal.

# Define service renewal interval (default 30 seconds)
eureka.instance.lease-renewal-interval-in-seconds=30
# Define service expiration time (default 90 seconds)
eureka.instance.lease-expiration-duration-in-seconds=90

Service Consumer

A. Fetching Services – Consumers request the service list from Eureka; the server returns a read‑only cache that is refreshed every 30 seconds.

# Cache refresh interval (default 30 seconds)
eureka.client.registry-fetch-interval-seconds=30

B. Service Invocation – After obtaining the list, Ribbon performs round‑robin load balancing. Eureka’s region/zone concept prefers instances in the same zone, falling back to other zones if necessary.

C. Service Deregistration – When a service shuts down gracefully, it sends a REST request to mark itself as DOWN, and the server propagates this status.

Service Registry Management

A. Expiration Removal – Eureka runs a scheduled task (default every 60 seconds) to remove instances that have not renewed their lease within 90 seconds.

B. Self‑Protection – If the heartbeat failure rate exceeds a threshold, Eureka protects existing registrations to avoid accidental removal, which may cause stale entries; clients should implement retries or circuit breakers.

# Disable self‑preservation (for local testing only)
eureka.server.enable-self-preservation=false

Spring Cloud Core Component: Ribbon

Ribbon is a client‑side load balancer for HTTP/TCP. When used with Eureka, Ribbon’s server list is populated from the Eureka registry, and it replaces the default IPing with NIWSDiscoveryPing to rely on Eureka for health checks.

Spring Cloud Core Component: Feign

Feign uses dynamic proxies. By annotating an interface with @FeignClient, Feign creates a proxy that builds request URLs from @RequestMapping metadata, sends the request, and parses the response. Feign works closely with Ribbon and Eureka to resolve service instances.

Spring Cloud Core Component: Hystrix

Hystrix provides circuit breaking, fallback, thread‑pool isolation, request caching, and monitoring. It isolates each dependent service in its own thread pool, preventing a slow or failing service from exhausting resources of other calls.

Spring Cloud Core Component: Zuul

Zuul integrates with Eureka, registers itself as a Eureka client, and obtains all service instances. It creates routes based on service names, and its filter mechanism allows pre‑processing and validation of API requests at the gateway level.

Summary

Eureka : Services register themselves and fetch the registry to discover peers.

Ribbon : Performs client‑side load balancing across multiple instances of a service.

Feign : Generates declarative REST calls using dynamic proxies and service metadata.

Hystrix : Executes calls within isolated thread pools and provides circuit‑breaker protection.

Zuul : Acts as an API gateway, routing external requests to internal services via Eureka.