DevOps @ Scale — Greek Tragedy in Three Acts
summary
A concrete scaling timeline for a DevOps team growing from 3 to 100 engineers, showing three stages: reactive firefighting, adding monitoring and processes, and finally proactive capacity work. Technologies named include Docker, Jenkins, Travis, JFrog (artifact repo), CloudWatch, Pingdom and New Relic; operational fixes include dependency caching, artifact-based rollbacks, on-call runbooks, incident reports and backlog items, illustrated by the left-pad npm outage and metrics such as ~15–20% stuck reactive, ~70% in the middle stage, ~10–15% proactive and a cited 42-item queue size.
AI-written summary · about
chapters (5)
- 0:00DevOps introduction
- 10:57Daily fires and chaos
- 27:11Reactive processes
- 41:20Proactive scaling
- 50:39Q&A
related talks
55mDevOps @Scale (Greek Tragedy in 3 Acts)
48mDevops@Scale
52mDevops @Scale
29mDevOps at Scale is a Hard Problem
36mDevOpsSup - Extended DevOps approach
45m200 Teams, 1 Goal: DevOps Maturity at Scale
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
22mOrganising a fast growing DevOps team a real life use case