Redundancy¶

Version: v4 · 2026-10-17 · History
Prime #: 287
Domain group: Interdisciplinary & Synthetic
Origin domain: Systems Thinking & Cybernetics
Also from: Engineering & Design (beyond software), Information Theory
Aliases: Duplication, Backup, N+1
Related primes: Robustness, Fail-Safe, Margin of Safety, Triangulation

Core Idea¶

Redundancy involves duplicating critical components or functions in a system so that if one element fails, the remaining ones can sustain overall operation, preventing total collapse.

How would you explain it like I'm…

Having a Spare

Redundancy is having a spare. If you only have one flashlight and the batteries die, you are stuck in the dark. But if you carry a second flashlight, you can still see. Having more than one of something important means if one breaks, the others keep working. That is redundancy. It is how we make sure things keep going even when something goes wrong.

Backups on Purpose

Redundancy is when you build something with extra copies of important parts on purpose, so that if one breaks, the others can keep the system running. Planes have multiple engines, cars have spare tires, and big websites have backup computers. The trick is that the copies need to fail for different reasons, not the same reason. If lightning fries all your backup computers at once because they share a single power line, the backups did not really help. Independence is the whole point.

Redundancy

Redundancy is a fault-tolerance design pattern that deliberately duplicates components or functions so the system keeps working when one of them fails. The crucial design variable is independence: if all the copies fail for the same reason at the same time, the redundancy is wasted. There are several configurations, including active-active (all copies run, any one is enough), active-standby (a primary runs, a backup takes over on failure), diverse-redundancy (different implementations of the same function, to avoid shared bugs), and voting (the majority of copies decides the output). Mathematically, the chance that N independent components all fail at once shrinks exponentially in N, which is what makes very high reliability possible.

Redundancy is a fault-tolerance design pattern characterized by deliberate duplication of components or functions whose failure would otherwise cause system failure, such that duplicates maintain function if any one of them fails. The central design variable is independence: redundant components must fail independently for the redundancy to deliver its intended fault tolerance, since correlated or common-mode failures defeat the design. Multiple configurations exist with distinct failure-coverage and cost trade-offs: active-active (all copies operate concurrently, any one suffices); active-standby (primary operates, standby takes over on detected failure); diverse-redundancy (different implementations reduce common-mode failures from shared bugs); and voting (majority among copies determines output, masking minority faults). Redundancy is also an information-theoretic principle: Shannon's channel-coding theorem shows that redundant encoding overcomes noisy channels, and the same idea handles component failure as "noise" at the component level. The probability of simultaneous independent failure of N components shrinks exponentially in N under independence, which is the load-bearing mathematical property enabling reliability targets such as the famous "five nines" of uptime.

Tensions in Practice¶

Failure diversity in tension with validation simplicity

Cross-Domain Echoes¶

See how this entry connects to another domain.

A backup has to remain usable

Broad Use¶

Aerospace & Aviation: Multiple independent control systems or backup flight surfaces to ensure safe flight if the primary system malfunctions.
Data Storage: RAID arrays (Redundant Array of Independent Disks) protect data by mirroring or distributing information.
Organizational Teams: Having more than one trained person for a key role so that if someone leaves or is absent, work can continue smoothly.

Clarity¶

Highlights the principle that some failures are inevitable, so the system should not rely on a single "point of failure"; duplication provides resiliency.

Manages Complexity¶

By accepting that no single part is infallible and introducing backups, designers reduce the need to make each part ultra-reliable—a simpler approach than guaranteeing 100% perfection.

Abstract Reasoning¶

Emphasizes a buffered or replicated design logic, illustrating "don't put all your eggs in one basket." This resonates with risk distribution and fault tolerance across domains.

Knowledge Transfer¶

Finance: Portfolio diversification to spread risk among multiple assets.
Public Policy: Having multiple layers (local, regional, national) that can provide social services if one layer fails.
Medicine: Dual-lumen catheters or parallel diagnostics ensuring continuous service even if one path fails.

Example¶

A server cluster with multiple machines running the same services ensures the website remains online if one server goes down.

Relationships to Other Abstractions¶

Current abstraction Redundancy Prime

Parents (3) — outgoing typed relations

Redundancy is a kind of Reserve Prime

Redundancy is a specialization of reserve in which the maintained surplus takes the form of duplicated components that can substitute on failure.
Redundancy is a decomposition of Self Checking Prime

Self-checking uses redundancy (the partially-independent path) and adds a comparator that extracts an error signal.
Redundancy is a decomposition of Two-Store Architecture Prime

Maintaining two oppositely-optimised persistent substrates presupposes redundancy (the duplicate path), adding a periodic transfer mechanism that consolidates rather than masks.

Children (20) — abstractions linked here by typed relations

Cylindrification Domain-specific is a kind of Redundancy

Redundancy is the broader abstraction this entry instantiates.
Lockstep (computing) Domain-specific is a kind of Redundancy

Lockstep computing duplicates computing channels executing identical steps so their outputs can be compared, the redundancy pattern's defining structure.
Log shipping Domain-specific is a kind of Redundancy

It remains its own entry because its identity is fixed by the primary and standby share a continuous log chain, backups are copied and restored in sequence, lag is monitored, and failover and data-loss boundaries.
Oversampling Domain-specific is a kind of Redundancy

What makes it its own entry: Sampling a signal substantially above its Nyquist rate to ease antialias filtering, distribute quantization noise and improve effective resolution after filtering or decimation.
Parvaresh–Vardy code Domain-specific is a kind of Redundancy

What makes it its own entry: An algebraic error-correcting code that encodes correlated polynomial evaluations so received words can be efficiently list-decoded beyond the Reed–Solomon radius.

▸ Show 15 more

Polar code (coding theory) Domain-specific is a kind of Redundancy
What makes it its own entry: A linear error-correcting code that recursively transforms channels into nearly perfect and nearly useless bit-channels, placing information only on the reliable ones.
Redundancy (engineering) Domain-specific is a kind of Redundancy
What makes it its own entry: Intentional duplication or diversification of components, information or functions so a system can tolerate failures or improve performance.
Tornado Code Domain-specific is a kind of Redundancy
**The equal-sized source blocks** carry the information to be preserved, and the configured sparse recovery blocks plus final outer-code symbols supply extra, partially independent equations from which missing blocks can be reconstructed.
Defense In Depth Prime is a kind of, typical Redundancy
Defense in depth specializes redundancy: it layers barriers FOR failure ABSORPTION UNDER ATTACK, with INDEPENDENCE OF failure MODES load-bearing and an optimizing adversary seeking the correlated breach.
Functional Redundancy (Degeneracy) Prime is a kind of Redundancy
Functional redundancy is a specialization of redundancy in which the duplicated elements are non-identical pathways that converge on the same function.
Convolutional code Domain-specific presupposes Redundancy
Convolutional code structurally presupposes Redundancy rather than being a subtype of it.
CSS Code Domain-specific includes Redundancy
logical information is distributed across more physical qubits.
Luby transform code Domain-specific presupposes Redundancy
**Redundancy** (`prime:redundancy`).
Marine Protected Area Network Domain-specific includes Redundancy
A marine protected area network contains deliberate replication against single-node failure.
Stabilizer code Domain-specific presupposes Redundancy
Stabilizer code structurally presupposes Redundancy rather than being a subtype of it.
Swiss Cheese Model (Layered Defense with Aligning Holes) Prime presupposes Redundancy
The Swiss cheese model is 'redundancy WITH the independence assumption made explicit and challenged' — it foregrounds the hole-correlation structure redundancy buries.
Perceivable Design Domain-specific is a decomposition of Redundancy
Perceivable Design is redundancy applied to essential signals so loss of one sensory channel does not eliminate the information.
Picture superiority effect Domain-specific is a decomposition of Redundancy
Stripping the human visual-verbal frame leaves Redundancy's independent-alternate-route structure: successful retrieval through either code is sufficient.
Two-person rule Domain-specific is a decomposition of Redundancy
The two-person rule is a security-specific redundancy pattern requiring two independent participants for critical access or action.
Parallel Independent Inspection Prime is a decomposition of Redundancy
Parallel independent inspection gains coverage by duplicating the inspection role across partially independent inspectors.

Hierarchy paths (12) — routes to 8 parentless roots

Redundancy → is a kind of Reserve → is a decomposition of Economy Of Force → is a kind of Allocation → presupposes Scarcity → is a decomposition of Constraint

Show alternative paths (11)

Not to Be Confused With¶

Redundancy is not Robustness because Redundancy is duplication of components for fault tolerance, while Robustness is capacity to withstand disturbance—the first is mechanism, the second is property.
Redundancy duplicates substitutable components or functions to maintain operation through a specified failure. A Data Backup Method retains recoverable digital data and the information needed to reconstruct a defined state after loss or unwanted change. They can overlap: NIST includes a noncollocated redundant secondary as one backup arrangement; neither duplication alone nor the word backup guarantees every recovery point or failure coverage.^[1]
Redundancy is not Safety Factor because Redundancy uses multiple pathways or components, while Safety Factor provides margin beyond requirements—the first is architectural duplication, the second is design margin.

References¶

[1] Swanson, M., Bowen, P., Phillips, A. W., Gallup, D., and Lynes, D. Contingency Planning Guide for Federal Information Systems. NIST Special Publication 800-34 Rev. 1 (2010), Appendix E CP-9(6), printed E-7 (PDF zero-based 136), and §5.1.6, printed 48 (PDF zero-based 61). Guidance on a qualifying secondary and shared-site failure boundaries, not evidence of a deployment. registry ↩