Course contentsShow
← System Design
Lesson 1336 of 1,91933. Reliability Engineering FoundationsFree lesson

Graceful Degradation

Designing systems to reduce functionality rather than fail completely when components are unavailable.

Graceful Degradation

What You'll Learn

You'll learn how to design systems that reduce functionality instead of failing completely when components become unavailable.

The Core Concept

Graceful degradation means your system stays partially operational even when parts of it fail, rather than crashing entirely. Instead of an "all or nothing" approach, you intentionally design fallback behaviors that preserve core functionality while sacrificing less-critical features.

Think of it like a car losing power steering—you can still drive the vehicle, it's just harder to turn the wheel. The car doesn't refuse to move just because one convenience feature failed.

How It Works

When a dependency (like a recommendation engine, payment gateway, or caching layer) becomes unavailable, your system detects the failure and switches to a degraded mode:

  • E-commerce checkout: If the recommendation service fails, show a static "popular items" list instead of personalized suggestions—but keep the checkout flow working
  • Social media feed: If image processing is down, display low-resolution thumbnails or placeholders rather than blocking the entire feed
  • Search engine: If personalized ranking fails, fall back to generic relevance scoring

The key is prioritizing critical paths. Identify what users absolutely need versus what's "nice to have," and ensure the critical path survives component failures.

Design Principles

  1. Isolate failures: Don't let one component's failure cascade to others
  2. Default to safe behavior: Pre-define fallback responses
  3. Communicate degradation: Let users know when features are limited (optional but honest)
  4. Monitor actively: Track when you're running degraded so you can fix root causes

Key Takeaway: Graceful degradation keeps your system useful during partial failures by intentionally sacrificing non-essential features while preserving core functionality—turning catastrophic outages into manageable service reductions.