The Site Reliability Workbook¶
Beyer, B., Murphy, N. R., Rensin, D. K., Kawahara, K., & Thorne, S. (2018). The Site Reliability Workbook: Practical Ways to Implement SRE. O'Reilly Media.
Cited by¶
8 citations across 8 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Controllability
- software engineering and infrastructure (deployability, rollbackability, feature-flag control surfaces, deployment authority structure; controllability-of-production as a core SRE concern; circuit-breakers, rate-limiters, and admin APIs as controllability levers)
This sourcePractitioner guide to operating production systems — deploys, rollbacks, feature flags, and incident response as production-control levers.; topical support, with the explicit 'controllability' framing being the prime's own synthesis.
- software engineering and infrastructure (deployability, rollbackability, feature-flag control surfaces, deployment authority structure; controllability-of-production as a core SRE concern; circuit-breakers, rate-limiters, and admin APIs as controllability levers)
Mechanisms¶
- Canary or Pilot Transition
- Its strength is that it is the cheapest way to buy real crossing evidence: a canary release surfaces boundary instabilities and adoption friction that no amount of planning can predict, at a stake small enough to walk back.
This sourceDefines canarying as a limited deployment that can be evaluated and rolled back with limited impact.
- Its strength is that it is the cheapest way to buy real crossing evidence: a canary release surfaces boundary instabilities and adoption friction that no amount of planning can predict, at a stake small enough to walk back.
- Phased Admission Trial
- At 5% the service runs as a canary alongside the incumbents
This sourceShows a release candidate running as a 5% canary beside the live version so its behavior can be compared with the control population.
- At 5% the service runs as a canary alongside the incumbents
- Release Readiness Review
- Staging behind flags and canaries turns an uncertain launch into a bounded experiment with a working undo — the operational readiness discipline formalized in modern site-reliability practice.
This sourceDescribes feature flags and canary releases as time-limited, partial production experiments that limit impact, support rollback, and form part of SRE launch-readiness practice.
- Staging behind flags and canaries turns an uncertain launch into a bounded experiment with a working undo — the operational readiness discipline formalized in modern site-reliability practice.
- Staged Integration Sandbox
- Its failure mode is that early rings are never perfectly representative — a canary carries less load, a mesocosm lacks the landscape's full ecology, so a combination can pass every ring and still surprise at full scale, and the confidence of "it passed staging" can outrun the realism staging actually had.
This sourceDefines a canary release as a partial and time-limited deployment evaluated against a control before wider rollout.
- Its failure mode is that early rings are never perfectly representative — a canary carries less load, a mesocosm lacks the landscape's full ecology, so a combination can pass every ring and still surprise at full scale, and the confidence of "it passed staging" can outrun the realism staging actually had.
- Staged Rollout Validation
- This is the canary release
This sourceDefines canarying as a small, time-limited production deployment evaluated before broader rollout.
- This is the canary release
- Substitutability Trial / Canary
- Because it ramps behind a rollback, it converts a risky cutover into a reversible experiment — and it is the only mechanism that measures a substitute's performance cost of substitution, not just its correctness.
This sourceA canary release turns a cutover into a staged, reversible experiment by comparing metrics on limited traffic and rolling back an unacceptable candidate.
- Because it ramps behind a rollback, it converts a risky cutover into a reversible experiment — and it is the only mechanism that measures a substitute's performance cost of substitution, not just its correctness.
- Witness Validation Test
- Witness validation runs a restore drill, a scheduled "game day": it takes the payments-service runbook and actually executes it against a clean environment.
This sourceDescribes scheduled game days that execute recovery procedures to test whether a service can actually be restored.
- Witness validation runs a restore drill, a scheduled "game day": it takes the payments-service runbook and actually executes it against a clean environment.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 8 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
- https://sre.google/workbook/table-of-contents/ ×4
- https://www.oreilly.com/library/view/the-site-reliability/9781492029496/ ×2
Registry ID ref:512858004836 · see in the full table