Migrating Enterprise Microservices From Cloud Foundry to Kubernetes
summary
An IBM Cloud UI of about 50 microservices is migrated from Cloud Foundry to Kubernetes, yielding measurable gains in CPU/memory efficiency, private intra-cluster networking, and faster Redis latency by deploying Redis via Helm inside worker nodes. Manifests become Helm charts; a VCAP_SERVICES shim preserves existing Node.js code so apps run on both platforms during cutover. Global traffic uses Akamai + Dyn geo load balancing to route between nine IBM Cloud Kubernetes clusters while NGINX logs and Prometheus provide replaced monitoring and metrics.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:43Agenda
- 1:07Ibm Cloud Console
- 1:46Console Architecture
- 3:14Cloud Foundry
- 3:26What Is Cloud Foundry
- 4:53Why Did We Switch
- 7:06Memory and Cpu Usage over Cloud Foundry
- 8:09The Cloud Foundry Flow
- 14:19Monitoring
- 21:06Closing Remarks
related talks
23mCloud Foundry and Kubernetes: A Peanut Butter & Jelly Application
31mNew Cloud Foundry Architectures and Features and their Performance Impact
35mTo Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
48mExtreme Devops using Kubernetes
38mThe Good, the Bad & the Ugly of Migrating Hundreds of Legacy Applications to Kubernetes
26mMicroservices With Cloud Foundry and Kubernetes
01h 08mIntro + Deep Dive - Provider IBM Cloud