Graceful degradation means a service continues to work in a limited form when part of it breaks. Rather than returning an error page, it drops non-essential features and keeps the core function available.
Why it matters
Most outages are partial. A recommendations service, search index, or third-party widget fails while everything else is healthy. If the page treats every dependency as mandatory, one small failure becomes a full outage. Degrading gracefully protects revenue and trust, and it makes your availability numbers better.
Example
An online store's product page calls five services. If the reviews service times out, the page can still render the product, price, and Add to Cart button, and show "Reviews are temporarily unavailable." If the recommendation engine is down, the page can fall back to a static list of best sellers.
Monitoring needs to see the degraded state. A plain up/down check returns 200 and reports everything fine, so add a keyword check for key content or expose component health on your status page.
Common mistakes
- Never testing the failure path, so the fallback itself throws an error.
- Using long timeouts that make the page hang before the fallback ever triggers.
- Degrading silently, so nobody knows a feature has been broken for days.
- Hiding the degraded state from your status page, which frustrates users who can see something is off.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.