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

What is Fault Tolerance?

Understanding fault tolerance as a system's ability to continue operating correctly despite component failures.

What is Fault Tolerance?

You'll learn: How fault tolerance enables systems to keep running correctly even when individual components fail.

The Core Concept

Fault tolerance is a system's ability to continue operating correctly—delivering expected functionality and maintaining acceptable performance—despite the failure of one or more of its components. Instead of crashing entirely when something breaks, a fault-tolerant system detects failures and adapts to work around them.

Think of it like a backup generator for a hospital. When the main power fails, the generator kicks in automatically. Patients continue receiving care without interruption—the system as a whole tolerates the fault in the primary power supply.

How It Relates to Availability

While availability (from earlier lessons) measures uptime percentage, fault tolerance is the mechanism that helps achieve high availability. A system with 99.999% availability needs fault tolerance techniques to handle the inevitable hardware failures, network issues, and software bugs without going down.

Key Characteristics

A fault-tolerant system typically includes:

  • Redundancy: Multiple copies of critical components (recall active-active and active-passive patterns)
  • Detection: Quickly identifying when a component fails (health checks, monitoring)
  • Isolation: Preventing one failure from cascading to other components
  • Recovery: Automatically switching to backup components or retrying operations
  • Graceful degradation: Continuing with reduced functionality when full recovery isn't possible

Unlike simply measuring MTBF or MTTR, fault tolerance is proactive—it's built into the architecture from the start.

Key Takeaway: Fault tolerance means your system anticipates failures and handles them automatically, keeping services running for users even when underlying components break—it's the "how" behind achieving high availability.