Experiences from using discovery services in a microservice landscape
summary
Compares Netflix OSS (Eureka + Ribbon), Docker Swarm, Amazon ECS with Application Load Balancer, and Google Kubernetes, and shows concrete code changes: two Spring Cloud annotations plus per-environment profiles that swap discovery without changing application logic. Demonstrates DNS in plain Docker failing round‑robin, Swarm’s routing mesh and static service IPs, Kubernetes’ pod/node autoscaling, and ECS path‑based ALB routing. Runs live demos including a rolling upgrade Java→Go, verifies health checks and resilience, and concludes code stays identical while only configuration changes avoid vendor lock‑in.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:50What happens if we try to combine these two tools
- 9:17Lets try it out
- 12:26Playing clean containers
- 15:13Docker Swarm
- 17:34Demo
- 22:35Kubernetes
- 24:06Google Cloud
- 26:19Google Cloud load balancer
- 29:11Amazon Elastic Load Balancer
- 32:09Load Balancer configuration
- 33:04Load Balancer in Amazon
- 33:58Programming model
- 35:26Code fragment
- 39:20Summary
- 40:25Demonstration
- 43:12Questions
related talks
31mMy journey into the world of microservices using spring cloud
27mMicroservices: Awareness and Discovery Pattern on K8s
49mMaking Sense Of Configuration and Service Discovery On Kubernetes
37mDistributed applications and Kubernetes: Frameworks or service meshes or both
01h 27mSpring Cloud at Netflix
05mLightning Talk - Netflix OSS on Kubernetes
59mJava microservices from Netflix OSS to Kubernetes
34mDistributed applications and Kubernetes