redundancy
Having more than one of a component, such as a server, power feed or network link, so the service keeps running if one of them fails.
In more detail
A redundant pair fails only when both copies fail at once, which is far less likely than one failing, provided the copies fail independently. Shared dependencies break that assumption: two servers on the same power strip, in the same building or running the same faulty update can fail together. It is the main tool of high availability, and it is proven only by testing that the spare really takes over.
Example
def pair(a): return 1 - (1 - a) ** 2 # either of two copies will doRelated terms
- high availability — Designing a system so it keeps working when one part fails, usually by running redundant copies with no single point of failure.
- single point of failure — One component whose failure stops the whole system working.
- failover — Switching work from a failed or unavailable system to a standby copy so the service keeps running.
- platform diversity — Deliberately using different vendors, software or providers for parts of a system so one flaw or outage cannot hit all of them.
Taught in
- Business Impact Analysis, RTO & RPO Modeling — Cybersecurity Fundamentals, GRC & Cryptography