Migrating a monolith to Cloud-Native (and the stumbling blocks)
summary
Claim: containerizing a monolith alone does not cut costs; AsgharLabs wraps a war file shoved into a container and sees OpEx rises after containerization. Practical tools and failures: Docker, Kubernetes/OpenShift/Nomad, WebSphere, AKS/EKS/IKS, F5 and Nagios show limits. Concrete surprises: a three-node cluster with work stuck on one node due to an in-app scheduler, support shifting to Stack Overflow, need for CI/CD pipelines, standardized logging, refactoring (repackaging, strangler pattern) and deliberate cost/accounting changes.
AI-written summary · about
chapters (18)
- 0:00Cloud-native migration challenges
- 1:17Containerization promises
- 3:45Lifting monoliths myths
- 8:18Re-platforming legacy apps
- 10:45Repackaging to microservices
- 11:50Strangler pattern refactoring
- 13:12Velocity and team needs
- 15:21Avoiding tooling double-ups
- 17:26Migration failure reasons
- 18:29Automation in cloud-native
- 20:17Monolith to microservices
- 21:59Cultural shifts for self-orchestration
- 23:43Collaboration beyond meetings
- 25:27Visibility tools limits
- 26:29Cloud economics surprises
- 27:53Kubernetes support models
- 29:15Key migration questions
- 30:39Summary
related talks
25mMigrating a monolith to Cloud-Native and the stumbling blocks that you don’t know about
26mOn Prem to Cloud Native
28mMoving a Monolith from AWS EC2 to K8
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies
18mRe-Architecting Monoliths Into Kubernetes Microservices at Million-User Scale: Hard...
20mApplication Modernization: From Concept to Kubernetes
44mMigrating a Monolith to Kubernetes
01h 02mContainers in Production: It’s Like Orchestrating Cats