Graceful Degradation
Capacity shortage can let optional features displace core flows.
- PriorityPriority: Core functions stay available first.
- ReductionReduction: Optional work is selectively suspended.
- RecoveryRecovery: Functions return after stable recovery.
Context
Why this is important
Preserve usability through explicit priorities.
Preserve usability through explicit priorities.
Graceful Degradation: inspect the decision
The shop example uses the existing shared database and seven modules. Any added service or deployment model is a hypothetical extension. During a traffic spike, shop checkout remains the priority. Live recommendations are disabled first, then product images use lower resolution, while price and payment validation continue. Product and operations teams agreed on this order in advance. A load test confirms that the core transaction remains stable within the assumed capacity. Optional features are restored in stages after load subsides.
This is how you read the picture
- Priority Priority
- Reduction Reduction
- Recovery Recovery
| Concept | Meaning | Review question |
|---|---|---|
| Priority | Core functions stay available first. | Which shop feature is paused first? |
| Reduction | Optional work is selectively suspended. | Which operating rule controls the degradation level? |
| Recovery | Functions return after stable recovery. | Which signal permits a return to full functionality? |
Benefits & limitations
Helps if:
- Preserve usability through explicit priorities.
- Rank functions by business value and test degradation levels.
Boundaries
- Without agreed priorities, reduction can damage core value.
- Degradation needs recovery criteria so optional features return after the traffic spike.
In practice
- Rank recommendations, image quality, catalogue display, and checkout by business value, and agree before testing which functions degrade first under overload.
- Generate a load spike and activate degradation stages one at a time; measure checkout success, price validation, and response time rather than CPU alone.
- Reduce load gradually and check whether optional functions return in a controlled way without overloading the checkout that has just stabilized.
Read the detailed explanation
Graceful degradation ranks functions by business value and selectively reduces less important capabilities when capacity is constrained. The system remains usable within an agreed scope even when optional functions fail.
The strategy defines priorities and acceptable substitute quality across components. It needs an activation signal, clear communication, and conditions for returning to normal operation.
The shop example uses the existing shared database and seven modules. Any added service or deployment model is a hypothetical extension. During a traffic spike, shop checkout remains the priority. Live recommendations are disabled first, then product images use lower resolution, while price and payment validation continue. Product and operations teams agreed on this order in advance. A load test confirms that the core transaction remains stable within the assumed capacity. Optional features are restored in stages after load subsides. fallback degradation and load shedding help compare this decision with adjacent concerns.
Check your understanding
Test yourself in three stages
ReadingCheck in the picture
Which shop feature is paused first?
View the solution with justification
Recommendations as an optional feature; checkout remains prioritized.
ApplyingTransferred to a new situation
Which operating rule controls the degradation level?
View the solution with justification
Measured load and agreed priorities determine which feature is reduced.
EvaluateWeighing an alternative
Which signal permits a return to full functionality?
View the solution with justification
Stable spare capacity across the defined recovery window.
Explore further
These building blocks continue the thoughts of this page.