Evolution of SRE and Rising Need of SRE Catalyzers
summary
LinkedIn recounts SRE rising from a seven‑person site‑ops crew in 2010 to backing product growth to 5M members by 2017 at ~30% YoY, and credits concrete practices: site‑up first, developer ownership, and TPMs as metric‑oriented catalysts. A concrete example cuts noisy on‑call alerts from 400 alerts → 100 impactful by running focused weeks‑long remediation (data, buy‑in, exit criteria) and using configuration‑as‑code and source control for rollbacks; TPMs measure, trace, prioritize, and security teams enforce guardrails.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:25What a technical program manager has to offer
- 1:09Tall Gaunt Fire
- 2:47Peak Traffic
- 3:22Knee of Growth Curve
- 4:21SRE Core Principles
- 6:08SRE Global Presence
- 6:28SRE Journalist
- 6:43Fox and Hedgehog
- 7:40Catalysts
- 10:16Expectations
- 10:33Technical Program Manager
- 11:09Expectations from TPMS
- 14:27TPMS
- 17:42Blind Spots
- 18:52Feedback Loop
- 19:18FiveStep Plan
- 19:32Approach the Feedback
- 20:48Takeaways
- 20:59Measure
- 21:35Security
- 23:03Microservice Architecture
- 23:23SRE Challenges
- 24:13How to maintain that
- 25:14Lessons
- 25:34Conclusion
- 26:24Catalyzers
- 27:56Questions
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
23mSite Reliability Evangelism: Practice Start-up within an Established...
25mSRE in the Third Age
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
30mThe Path to SRE
25mSRE Guiding Principles & Transformational Framework
27m20 Years of SRE: Highs and Lows
36mWhat Makes a Good SRE: Findings from the SRE Survey