Scaling DevOps in Complex Environments: Challenges, Failures, and Successes
summary
Scaling DevOps across large, distributed teams reports concrete numbers and tools: 72% legacy of enterprise architectures persist, knowledge workers waste 12 hours/week chasing data, and breaches cost about $4.35M with organizational churn costing ~$13M. Successes come from Terraform, containerization, microservices and phased migrations rather than big-bang rewrites. Shared KPIs, automation, observability and a culture of “you build it you run it” enable higher deployment frequency; case studies from Netflix and Amazon show reduced outages and faster recovery.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 1:51What is DevOps and its goals
- 3:21Benefits of scaling DevOps
- 4:42Challenges in scaling DevOps
- 7:13Organizational silos and their costs
- 9:01Strategies for scaling DevOps
- 10:06Modernizing legacy systems
- 12:55Cultivating DevOps culture
- 15:06Case studies from Netflix and Amazon
- 16:51Conclusion and key takeaways
related talks
52mDevops @Scale
25mFrom Ops to Impact: Scaling Engineering Velocity
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
45m200 Teams, 1 Goal: DevOps Maturity at Scale
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
47mOvercoming Obstacles to DevOps
28mLeading Changes in DevOps Organizations
29mDevOps at Scale is a Hard Problem