Java microservices from Netflix OSS to Kubernetes
summary
Company migrates a Java microservices stack from Spring Boot + Netflix OSS (Eureka, Feign, Ribbon, Hystrix, Zuul) on EC2 with Spinnaker/blue‑green to Kubernetes + Helm, rolling updates. Original setup suffers a Git-backed config server outage (two days), large artifact sizes, low VM utilization and $5,000/month infra; first Kubernetes service deploys in two weeks, templates spin new services in an hour, test environments drop to ~$500/month, node utilization rises toward 80–90%, and teams refocus on product rather than plumbing.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:54Architecture requirements
- 17:18Netflix OSS issues
- 20:58Why Kubernetes
- 25:55Kubernetes migration
- 34:06Results and benefits
- 47:13Conclusions and advice
- 50:06Q&A
related talks
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
14mMigrating and running production services in Kubernetes
48mKubernetesize your Java application
25mKubernetes for Java Developers
40mCloud Native Java
54mJava based microservices, containers, Kubernetes - how to
39mMicroservices & Kubernetes in a High-demand Environment: The Experience
53mNext Generation Microservices