Skip to content
BENIBIX Learn

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.

Infrastructure📟 Reliability

Graceful Degradation

The key jobs keep working when one part fails. The extras switch off.

Graceful degradation means a system keeps its most important jobs working when part of it fails. It turns off the extras instead of failing all at once. A shop might hide its product tips when that service is slow, but still let people pay. The team decides ahead of time which parts can switch off. Users see a plainer page rather than an error.

Example
Jack's news site loses its comments service. The articles still load, with a note that comments will be back soon.
Why it matters
Most failures hit one part, not all of it. Planning for that keeps the paths that earn money open.
Full entry
Infrastructure📟 Reliability

Fault Tolerance

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

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.
Full entry

In one line

Graceful Degradation
The key jobs keep working when one part fails. The extras switch off.
Fault Tolerance
A system that keeps going with no break, even when a part has failed.