Towards a culture where everyone is responsible for downtime
summary
A retrospective of one software vendor’s shift from product-development teams to cloud service teams running thousands of customer instances, covering the cultural and operational changes rather than core code changes. Topics include impacts on system architecture, creating Standard Operating Procedures, defining SLAs/SLOs, handling blast radius, noisy neighbors, SRE practices, and overall risk-thinking to make everyone responsible for service unavailability.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 5:08Downtime responsibility culture
- 17:35Evolving teams
- 25:17Architecture Q&A
- 27:47Conclusion
related talks
45mToward a Culture Where Everyone Is Responsible for Outages
22mLeading software teams with context (visibility)
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
07mIterative Enterprise SRE Transformation
36mRebooting Culture
18mWe need to talk about SRE burnout
54mCloud Native Culture