The Cloud Provider Lift and Shift: Staying Mobile with Node.js and Kubernetes
summary
Demonstrates lifting a real Node.js service to multiple clouds by provisioning three managed clusters (AWS EKS, GKE, Azure AKS) with Terraform, deploying the same Express app backed by Node.js app with MySQL and Redis via kubectl, and observing that one app becomes externally reachable while the others finish load‑balancer setup; EKS requires extra EC2 worker nodes, Terraform reduces per‑provider differences, and the whole workflow completes in about 30–40 minutes so multi‑cloud lift‑and‑shift is practically feasible. Terraform as adapter
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:11Vendor Consumer Marketplace Cycle
- 5:03Lockin Phase
- 6:05Plugging in
- 6:24Adapter phase
- 7:06Container technologies
- 7:46Kubernetes as a standard
- 9:33What is Lift and Shift
- 9:53Why should the Node community care
- 10:06What is Node good for
- 12:39Avoiding vendor lockin
- 13:24The more mature an application is
- 13:50Should you just leave now
- 14:16Prototype to Compare
- 15:31Use the Right Provider
- 16:39Avoid Legacy Lockin
- 17:52Flexibility
- 18:21The hard way
- 19:11Demo
- 22:56Terraform
- 24:22Barrier to Entry
- 25:48Running Kubernetes on EKS
- 29:41The Easy Way
- 30:44The Last Takeaway
related talks
35mKubernetes journey
41mAn Adventure in Multi-Cloud with Kubernetes
26mCloud kubernetes Native Applications
33mKubernetes-Driven Multi-Cloud Deployments: Maximizing Scalability and Flexibility
34mCloudy With a Chance of Kubernetes: Going From One To Three Cloud Providers
38mThe Reality of Porting Kubernetes Apps Across Cloud Providers
36mThe Architecture of a Multi-Cloud Environment with Kubernetes
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization