Practical Cloud Native: What Works, What Doesn't
summary
Company moves from VMs to AWS, containers and Kubernetes, cutting provisioning from weeks to minutes and achieving 3,000 releases in four weeks (roughly 30,000 per year versus ~50 before). Migrating one microservice per VM to containers yields a 40% cost reduction. Continuous delivery pipelines, feature flags and canaries, a queue-backed change API, request-wide IDs for structured logs, nightly runbook exports to S3, and chaos tests drive resilience; change failure rate falls from ~15–20% to under 2%. Team Topologies-style platform and enabling teams provide self-service guardrails for safe, rapid delivery.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:00Moving to the cloud
- 2:55The cloud native approach
- 6:15Why cloud native?
- 10:34What changes?
- 10:591. Deployment
- 15:092. Architecture
- 21:043. How you build things
- 26:414. How you test things
- 30:215. How you support things
- 31:356. What your organization looks like
- 35:47Outro
related talks
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
30mBuilding Applications in the Cloud: Best Practices
01h 02mTransforming IT pros to DevOps gurus: Ssecure your new tech stacks
42mCloud Native Applications
12mKeynote: What It's Like to Bring DevOps to a Software Factory in Central America
32mCloud Native Progressive Delivery
43mMigration to the Cloud, DevOps Perspective
36mPanel Discussion: Leveraging Cloud Native Technology to Transform Your Enterprise