Evolving to Cloud Native
summary
Practical playbook for moving a legacy portfolio to cloud: assess each app for tech stack, startup time, filesystem and vendor dependencies, and 12‑factor gaps, cataloging results (assess portfolio (~400 apps, 3–4 hr/app)). Run pilots, refactor incrementally—most apps need weeks not months to modernize (refactor measured in weeks per app)—or choose lift‑and‑shift, containers, a platform like Cloud Foundry/Kubernetes, or serverless where latency and billing fit. Real outcomes: improved dev→prod parity, faster deploy cadence (example cited: 3,000 deploys/month (Scotiabank)), but watch cold starts and runaway costs.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:50Defining cloud native computing
- 8:02Cloud native as engineering practice
- 11:07Cultural shift in DevOps
- 13:36From pets to cattle in infrastructure
- 17:30Cloud as commodity and abstraction
- 21:02Speed and continuous delivery
- 24:36Twelve Factor App explained
- 35:08Microservices and modularity
- 41:45Serverless and abstraction layers
- 52:21Assessing cloud readiness
- 59:46Q&A and closing remarks
related talks
41mModernizing Legacy Apps - Platforms and Strategies
30mThis Old App, a guide to renovating apps for the cloud
45mThe Ultimate Checklist to Make Your Applications Cloud Native
30mThe transformative power of modern applications
06mAccelerate Application Delivery with a Cloud-Native Mindset
30mUsing the Theory of Constraints to Prioritize Applications for Migration to Cloud Foundry
27mCloud Native Transformation Patterns
15mHow to build a winning app modernization strategy & deliver on it
