Before you use it
- Use when
- Demand spikes or a dependency fails and the full service cannot be delivered reliably.
Keep this limit in mind
- A complex rarely tested fallback can be less reliable than the main path; keep degradation simple and exercise it.
Current editorial reading
Define the useful minimum
Name the core outcome, the optional work to remove, the condition that activates the mode and the condition for leaving it. Explain any lost features or freshness to users. For example, an internal reference tool could serve an allowed cached edition while enrichment is unavailable, with the edition date visible. Whether stale information is acceptable depends on the task.
Keep the recovery path simple
In a controlled test, make the dependency unavailable and verify both the remaining user task and the resource or dependency demand. Also test the return to normal service. A mode that uses fewer calls but breaks required consistency is not an acceptable result. Avoid elaborate fallback chains that receive little testing; the alternate path needs maintenance too.
Take it with you
Write one failure scenario and one pass condition for the core task. Exercise it before treating the degraded mode as a recovery option.
Sources and evidence (2)
What we checked
Google SRE describes graceful degradation as reducing work and calls for explicit activation metrics and behavior.
Selected official passages read on 2026-10-04. The specific cached-reference example and exit check are editorial applications, not measured outcomes.
Addressing Cascading Failures · Load Shedding and Graceful Degradation
AWS recommends identifying core functionality and testing it during dependency failure.
Selected official passages read on 2026-10-04. This supplies the previously unlinked AWS basis; business requirements determine acceptable degradation.
REL05-BP01 Implement graceful degradation to transform applicable hard dependencies into soft dependencies · Desired outcome; Common anti-patterns; Implementation guidance
AWS warns about inconsistent partial transactions and calls for simpler, tested failure paths.
Selected official passages read on 2026-10-04. No general permission to sacrifice consistency or serve stale data is implied; circuit-state terminology on this page was not used.
REL05-BP01 Implement graceful degradation to transform applicable hard dependencies into soft dependencies · Common anti-patterns; Implementation guidance on core requirements and failure paths
Editorial sources (2)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTest the simpler service mode before relying on it
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaOpen the circuit when a dependency keeps failing
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
Google and AWS overload guidance recommend load shedding or graceful degradation to preserve core useful work when total demand exceeds available capacity.
Which work may be dropped or degraded is a product and safety decision, not only a technical one.
Addressing Cascading Failures · Load shedding and graceful degradation
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details
