You Build It You Run It sounds great... but it won’t work here!
summary
Enterprise case for You Build It You Run It: moving from one team/one microservice to 40 teams and 120 microservices in 2.5 years yields daily deploys, target 99.9% availability and minutes TTR by making product teams own deployments and on‑call. Uses PagerDuty + ServiceNow + Slack for automated incident channels, maps availability to financial exposure (2–3 nines), and shows concrete metrics — scheduler team with rework rate 10% vs legacy 75% and much shorter restore times.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:56What is You Build It You Run It
- 10:23Developers won't want to do it
- 11:27Give your developers what they need
- 14:11It won't scale to lots of teams
- 16:23Balance financial exposure and on-call costs
- 20:53Trust your people to do the right thing
- 22:59There'd be no incident management
- 25:41Make incident management self-service
- 28:22Developers would be firefighters
- 31:41Measure and eliminate BAU work
- 35:09We can't hire a DBA for every team'
- 37:41Make repeatable, specialist tasks self-service
related talks
42mOperability and You Build It You Run It
29mYou build it, you run it.
43mTo make mistakes is human. To auto-deploy it is DevOps.
50mYou build it, you run it (why developers should also be on call)
33mFrom 0 to DevOps in 80 days
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
06mDeploy Like a Startup, Scale Like an Enterprise
30mBringing DevOps Success to Every App, Tool & Role in Your Org