Skip to main content

Service Discovery: Netflix Eureka and Consul

Learn Service Discovery: Netflix Eureka and Consul (Phase 4 · Service Discovery and API Gateway (Core), Microservices) with worked examples, diagrams and interview questions. Free on JavaSchoolLab.

Why service discovery? • In dynamic environments (containers, autoscaling) instances start, stop and change IP/port constantly: hard-coded URLs do not work. Service discovery lets services register themselves and clients look up healthy instances by logical name ( catalogue-service ). • Client-side discovery : the client queries a registry and load-balances itself (Eureka + Spring Cloud LoadBalancer, Consul). Server-side discovery : a router/load balancer does it (Kubernetes Service/kube-proxy, AWS ALB, Ingress): the client calls a stable DNS name. • On Kubernetes you usually do not need...

More lessons in Phase 4 · Service Discovery and API Gateway (Core)