Reliability Trade-off Vocabulary
5 exercises — Practice vocabulary for reliability trade-offs: reliability vs. feature velocity, downtime budget calculations, appropriate reliability, and the cost of additional nines.
0 / 5 completed
1 / 5
An engineering director says: "We're trading reliability for feature velocity this quarter." A stakeholder asks what this means. Which explanation is correct?
Making the reliability-vs-velocity tradeoff explicit is healthier than pretending it doesn't exist — teams always make this tradeoff implicitly; the SLO/error budget framework makes it visible and governable.
The tradeoff is real: every deployment is a reliability risk. When the error budget is healthy (lots of budget remaining), the team can afford to move fast and accept more risk. When the budget is depleted, they must slow down. Error budgets formalise this: a healthy budget = green light for velocity; depleted budget = mandatory reliability focus. The problem with "we're trading reliability for velocity" without error budget governance is that there's no agreed endpoint — teams often don't know how much reliability they've traded away until they have a major incident. The SRE framework's answer is to make the tradeoff bounded and monitored rather than open-ended.
Key vocabulary:
• reliability-velocity tradeoff — the tension between shipping faster (more risk) and operating reliably (more caution)
• deployment risk — the probability that a new deployment will cause a reliability incident
• error budget governance — using SLO/error budget metrics to make the reliability-velocity tradeoff visible and bounded
The tradeoff is real: every deployment is a reliability risk. When the error budget is healthy (lots of budget remaining), the team can afford to move fast and accept more risk. When the budget is depleted, they must slow down. Error budgets formalise this: a healthy budget = green light for velocity; depleted budget = mandatory reliability focus. The problem with "we're trading reliability for velocity" without error budget governance is that there's no agreed endpoint — teams often don't know how much reliability they've traded away until they have a major incident. The SRE framework's answer is to make the tradeoff bounded and monitored rather than open-ended.
Key vocabulary:
• reliability-velocity tradeoff — the tension between shipping faster (more risk) and operating reliably (more caution)
• deployment risk — the probability that a new deployment will cause a reliability incident
• error budget governance — using SLO/error budget metrics to make the reliability-velocity tradeoff visible and bounded