Back to glossary

Graceful Degradation

A system design approach where functionality progressively reduces in quality rather than failing completely when components malfunction, maintaining core functionality even under adverse conditions.

Graceful degradation ensures users always get some value, even when parts of the system fail. Instead of showing an error page when the recommendation engine is down, the site falls back to showing popular items. If the AI assistant is overloaded, the system switches to pre-written FAQ responses. The experience is reduced but never broken.

Implementing graceful degradation requires defining fallback strategies for every external dependency and non-critical feature. Each fallback has a trigger condition (timeout, error rate threshold, circuit breaker opening) and an alternative behavior (cached data, default values, simplified logic, feature disabled with explanation).

For AI-powered products, graceful degradation is essential because AI components have more failure modes than traditional software. Model APIs go down, inference latency spikes, output quality degrades, rate limits are hit, and costs surge. A well-designed degradation strategy maps each failure mode to a specific fallback: cached predictions when the model API is slow, rule-based logic when the model is unavailable, and truncated features when costs exceed thresholds.

Related Terms