On Prem to Cloud Native
summary
Claims that lift and shift is the most expensive migration and that big bang rewrites fail get justified with specifics: chargeable data transfer, hot vs cold storage costs, and higher VM provisioning costs. Concrete steps: replatform databases to managed services (Azure SQL, RDS), containerize macroservices, apply a strangler fig refactor or fork endpoints, then move to serverless so serverless only runs when needed. AI agents require clean code to actually automate the split.
AI-written summary · about
chapters (8)
- 0:00Cloud migration challenges
- 2:49Migrations fail without drivers
- 5:21Lift and shift is expensive
- 8:53Big bang migrations fail
- 10:39Cloud native roadmap
- 13:12Lift and shift to microservices
- 17:03Serverless cost reduction
- 19:23Clean code in AI
related talks
20mApplication Modernization: From Concept to Kubernetes
31mMigrating a monolith to Cloud-Native (and the stumbling blocks)
25mMigrating a monolith to Cloud-Native and the stumbling blocks that you don’t know about
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization
33mNavigating the Seas of Transformation: Migrating from EC2 to Kubernetes
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration
45mFrom Laptop to Cloud: Developing Cloud Native Applications with Containerized Databases
25mBreaking Free From the Cloud: Banking on Self-Hosted Kubernetes