Splicing SRE DNA Sequences in the Biggest Software Company on the Planet
summary
Azure creates an SRE org from scratch across ~58 service offerings and >200 company services, hires a small core team (~6–7 pioneers from Google/Amazon/etc.), and uses a production readiness document and guided “service roasts” to produce prioritized backlogs. The team builds an operational intelligence team for high‑fidelity SLO metrics and a fully automated demand shaping service that balances capacity across regions, cutting manual toil and proving SRE pilots on IoT and storage.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:27Welcome
- 1:52organisms
- 3:54Azure service offerings
- 4:16Scale
- 6:45Production Incidents
- 10:16Scaling Operational Models
- 12:30Cultural Engineering
- 16:45Where is SRE
- 19:28Symptoms of Success
- 24:20SRE Engagement Types
- 26:23Production Readiness
- 28:52IoT
- 31:32Storage
- 33:44Production virtuous cycle
- 34:51We dont own all this
- 35:55Metrics and Monitoring
- 38:10Incident Response
- 39:14Learnings Critical Moves
- 42:28Conclusion
related talks
41mBuilding an SRE Capability Inside a Large Organization
43mSRE From Inception to Global Scale
18mSRE Engagement Model Transition in Building and Expanding SRE Team
30mThe Path to SRE
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
21mSRE: An incomplete guide to cultural Narnia
28mEvolution of SRE and Rising Need of SRE Catalyzers