Containerization ≠ Modernization: Kick-Start Your Transformation Journey
summary
Project work spans 50+ enterprise transformations and 8,000+ AWS Lambda functions, with real‑time data pipelines and GenAI copilots used to cut time‑to‑value. Concrete claims include release frequency ↑ 5× and infra spend ↓ 60%. Recommended levers are domain‑driven decomposition, serverless first (S3, RDS, SQS over premature Kafka/Kinesis), FinOps rework for consumption billing, and a strangler‑fig refactor path to replace the 18–24 month “jugaad” shelf life.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:52The CFO's corridor panic
- 5:41The managed services nudge
- 7:16Jugaad isn't a strategy
- 9:24Buy or build?
- 13:49Enter modernization – The real one
- 14:03The cost of stale code
- 14:31Data as first-class citizen
- 16:49Serverless first, not Kubernetes always
- 19:136 dimensions of modernization
- 21:06Start with small wins
- 21:42Modernization is a culture, not a phase
- 23:03What "Good" looks like
- 23:53Key takeaways
- 24:23Outro
related talks
30mThe transformative power of modern applications
14mApp modernization on AWS, described by engineers who have done it
35mContainers and AWS Lambda: Choosing optimal compute for modern apps
29mHow AWS accelerates business transformation
36maccelerates its modernization journey with
29mMigrate and Modernize to Achieve Your Business Outcomes
26mRealizing the Business Value of Modernizing
35mModernizing Applications with Containers and Serverless