Building Successful SRE in Large Enterprises—One Year Later
summary
Google’s CRE program claims enterprises are the easiest early adopters and reports concrete wins: Home Depot grows from 0 to ~800 services with SLOs in a year (≈50/month), Shopify and Evernote are customers, and regulated firms map risks to SLOs and error budgets. Success hinges on willingness to do the work, not raw engineering skill. Start small: one application first, teach SLOs (a week or two) then iterate; a full soup‑to‑nuts rollout takes ~9–12 months. Monitoring gaps, blameless postmortems and risk stack‑ranking are the practical tools used.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:33Quick Summary
- 5:31Google SRE
- 6:46Enterprise SRE Love
- 10:28The Willingness Period
- 13:00Not Hard
- 15:19Customer Quotes
- 17:36Start with One
- 19:34Regulated Industries
- 20:50Risk vs Innovation
- 23:11Stack Rank
- 23:51S3 for Regulated Industries
- 26:28Dont do it all at once
- 27:13Dont enforce it
- 28:34Closing thoughts
- 29:58Resources
- 31:23Customer Consultations
- 32:55Customer Interaction
related talks
41mAn Introduction to SRE at Google (with DevOps Focus)
41mBuilding an SRE Capability Inside a Large Organization
16mSRE in Transition: From Startup to Established Business
19mCrafting an SRE Roadmap for Enterprise Success
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
30mThe Path to SRE
45mClearing the Way for SRE in the Enterprise
14mRun, Walk, Crawl, or How We Failed Our Way to SLO Readiness