The Value of Reliability
summary
Argues reliability value isn’t just uptime seconds but measurable business impact: proposes stack labeling (attribute revenue to call-stack-like components), extends SLOs to measure failure concentration across user cohorts, and borrows AB-test economics (Bing paper) to rank fixes versus features; observes storage often absorbs most attributed value, backwash/churn is unknown and must be measured, and recommends numeric KPIs and cross-team coalitions to win engineering prioritization.
AI-written summary · about
chapters (8)
- 0:00Defining the problem
- 1:13Critiquing standard models
- 3:38Limitations of current metrics
- 7:59Emerging reliability models
- 12:41Advanced diagnostic approaches
- 15:40Prioritizing engineering work
- 20:58Strategic communication
- 25:17The future of reliability
related talks
27mThe Perverse Incentives of Reliability
18mMeasuring Reliability Culture to Optimize Tradeoffs: Perspectives from an...
34mReliability and Engineering Requirements
22mImproving Reliability by Data-Driven Engineering & Culture Changes
45mPanel Discussion: Is Reliability a Luxury Good?
15mShit, our Site is Down! Let's build a culture of reliability
30mThe 'Success' in SRE Is Silent
06mLightning Talk: Reliability Engineering for Humans
