high availability

Designing a system so it keeps working when one part fails, usually by running redundant copies with no single point of failure.

In more detail

High availability starts with spreading copies across independent failure domains and removing single points of failure. It is different from recovery: a highly available database copies a bad delete to its standby just as faithfully as a good write, so backups are still needed.

Example

In AWS this usually starts with running across two or three availability zones.

Related terms

Taught in

References

Certification courses