Web Operations¶
Allspaw, J., & Robbins, J. (2010). Web Operations: Keeping the Data on Time. O'Reilly.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Configuration Drift
- The change pressure is the steady stream of production incidents: at 3 a.m. an engineer SSHes into one node and hand-raises a connection limit "temporarily" to clear an outage, and never updates the playbook.
This sourceOperational accounts of ad-hoc production hotfixes and out-of-band changes that bypass the system of record under incident pressure.
- The change pressure is the steady stream of production incidents: at 3 a.m. an engineer SSHes into one node and hand-raises a connection limit "temporarily" to clear an outage, and never updates the playbook.
- Procedure-Work Mismatch
- Nuclear operations' peer-review and operating-experience programs are the structural ancestor of blameless postmortems and shared incident databases in software reliability.
This sourceTreats runbooks lagging architecture and the blameless postmortem as the move surfacing enacted operational reality.
- Nuclear operations' peer-review and operating-experience programs are the structural ancestor of blameless postmortems and shared incident databases in software reliability.
- Rehearsal
- the whole-action property means exercising the full response — detection, paging, diagnosis, mitigation, communication — not just unit-testing a failover; the feedback loop is the blameless post-mortem that updates the runbook;
This sourceEstablishes post-incident review (the blameless post-mortem) as the feedback loop that updates the runbook after an incident or exercise.
- the whole-action property means exercising the full response — detection, paging, diagnosis, mitigation, communication — not just unit-testing a failover; the feedback loop is the blameless post-mortem that updates the runbook;
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 3 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.
Registry ID ref:9a54c1a54ffd · see in the full table