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.
High Availability (HA)
A service built to stay up nearly all the time. Each part has a spare copy.
High availability means a service stays up almost all the time. It is built by running spare copies of each part, so no one failure stops it. When one copy fails, traffic moves to another, often in seconds. Availability is counted in nines. 99.9% is three nines, and 99.99% is four.
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.
In one line
- High Availability (HA)
- A service built to stay up nearly all the time. Each part has a spare copy.
- Fault Tolerance
- A system that keeps going with no break, even when a part has failed.