Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
10 results for “Graceful Degradation”
Graceful Degradation
Continuing to deliver reduced but useful function when a dependency fails, instead of failing the whole request.
Brownout
Deliberately reducing the quality or completeness of every response under load, rather than serving some requests fully and rejecting others.
Fallback Strategy
What a caller does instead when a circuit breaker is open — the part of the pattern that determines whether failing fast helps anyone.
Harvest and Yield
A refinement of CAP that treats availability as a continuum — yield is the fraction of requests answered, harvest is the fraction of data reflected in an answer.
Priority Queueing
Classifying requests by business importance so that overload sheds the least valuable work first rather than an arbitrary slice.
Every deployment produces a small spike of 502s that the team has learned to ignore. Fix it.
The cause In flight requests are being severed because the instance terminates before the load balancer has stopped sending to it, or before existing requests c
Your service will exceed capacity by 30% during a known peak. Do you shed load or brown out, and how do you decide what goes first?
The decision Brown out first; shed only if that is not enough. They are complementary rather than alternatives, and brownout is strictly less harmful when it is
Graceful Degradation
Reduced but useful function when a dependency is gone.
Degradation Modes
Deciding in advance what is shed first and what is protected.
Soak Testing
Long runs that surface leaks and slow degradation.