# Fault Tolerance

> A system that keeps going with no break, even when a part has failed.

**Field:** Infrastructure  
**Category:** Reliability  
**Also known as:** Fault-Tolerant, Fault Tolerant System

## Think of it like

It is like a car with a spare tire already on. A flat does not even stop the trip.

## Definition

Fault tolerance is when a system keeps working, with no break at all, while a part has failed. Spare parts run at the same time as the main ones, so nothing has to switch over. High availability allows a short blip while traffic moves. Fault tolerance aims for no blip. It costs more, so it is kept for systems that can never pause.

## Example

A plane's flight computer runs as three copies at once. If one gives a wrong answer, the other two outvote it and the flight goes on.

## Why it matters

For some systems, even a few seconds down is not allowed. Fault tolerance is how they are built.

## Common mistake

Thinking it is just high availability by a new name. One allows a short break, and the other allows none.

## Three principles

- **No break.** Work goes on during the failure.
- **Spares run live.** Copies work side by side all the time.
- **Costs more.** Kept for what can never pause.

## Related terms

- [High Availability (HA)](https://learn.benibix.com/term/infrastructure/high-availability)
- [Health Check](https://learn.benibix.com/term/infrastructure/health-check)
- [Circuit Breaker Pattern](https://learn.benibix.com/term/development/circuit-breaker)
- [Single Point of Failure](https://learn.benibix.com/term/development/single-point-of-failure)
- [Redundancy (Systems)](https://learn.benibix.com/term/infrastructure/redundancy)
- [Graceful Degradation](https://learn.benibix.com/term/infrastructure/graceful-degradation)

## Told apart from

- [High Availability vs Fault Tolerance](https://learn.benibix.com/compare/high-availability-vs-fault-tolerance): People use the two names as one idea, and they are not. With high availability, a service may blip for a few seconds while traffic moves to a spare. With fault tolerance, spares run at the same time, so there is no blip at all. The second costs far more, so most sites only need the first.
- [Graceful Degradation vs Fault Tolerance](https://learn.benibix.com/compare/graceful-degradation-vs-fault-tolerance): People think any site that keeps running through a broken part is fault tolerant, but it may only be degrading. Fault tolerance keeps every feature working, because a spare takes over at once. Graceful degradation keeps only the key jobs, such as paying. It switches the extras off. The first costs more. The second is often enough.

![A load balancer at the top sends traffic down to three servers. The middle server is drawn dashed, and its health check says fail. The load balancer has stopped sending it traffic, and the two other servers carry on serving users.](https://learn.benibix.com/diagrams/inf-high-availability.svg)

---

Source: https://learn.benibix.com/term/infrastructure/fault-tolerance
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
