Addressing Cascading Failures¶
Beyer, B., Jones, Chris, Petoff, Jennifer, Murphy, & Richard, N. (2016). Addressing Cascading Failures. Site Reliability Engineering.
Cited by¶
4 citations across 4 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Chesterton's Fence
- It reveals the encoded constraint: without the delay, retries hammered a rate-limited upstream API and triggered a cascade of throttling that took down the service — the failure mode the artifact prevents.
Supported in partVerified against the work's full text
The SRE chapter supports the mechanism that undelayed client retries overload a backend and cascade, and prescribes backoff, but not a rate-limited upstream API incident.
“it can melt down and crash under the sheer load of requests and retries.”
- It reveals the encoded constraint: without the delay, retries hammered a rate-limited upstream API and triggered a cascade of throttling that took down the service — the failure mode the artifact prevents.
Mechanisms¶
- Capacity Warning Dashboard
- Collision Retry Protocol
- It misleads when retries are swallowed silently — an un-logged retry loop consumes the safety margin invisibly, so the first symptom is a latency cliff or an escalation storm when the space is already near full.
This sourceIllustrates a naive retry loop that continues after individual errors without logging each failed attempt.
- It misleads when retries are swallowed silently — an un-logged retry loop consumes the safety margin invisibly, so the first symptom is a latency cliff or an escalation storm when the space is already near full.
- Dependency Interaction Map
- Its strength is that it surfaces the interactions no pairwise cell can hold — the chained, indirect, load-triggered cascades where the damage is done by the path, not by any single pairing — and it ties each to a specific, cheap intervention on one link.
This sourceExplains how overload can propagate through dependencies as positive feedback, turning local service failures into cascading failures.
- Its strength is that it surfaces the interactions no pairwise cell can hold — the chained, indirect, load-triggered cascades where the damage is done by the path, not by any single pairing — and it ties each to a specific, cheap intervention on one link.
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? Read against the text for 1 of 4 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
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:a6fd0e06ea96 · see in the full table