Redundancy
Key Points
- Provides alternate paths or components
- Used to increase availability and fault tolerance
- Appears in networks, control systems, and infrastructure
- Can be active-active or active-standby
- Requires deliberate design at correct failure domain
- Common failure modes include split-brain conditions, failed failover, and misconfigured standby roles
Definition
Redundancy is the use of duplicate or alternate components so a system can continue operating after a failure. It supports availability and fault tolerance.
Concept
Redundancy is a system design term used for arranging backup components, links, or services so operation can continue when a primary element fails. It exists to reduce single points of failure and maintain service continuity. It is used in networks, industrial systems, cloud platforms, power systems, and control architectures. Redundancy may be implemented as duplicate hardware, alternate paths, standby nodes, or active-active resource pairs.
Explainer
Redundancy is an engineering approach that provides duplicate or alternate components, links, or services so a system can continue operating when part of it fails. It works by arranging standby or parallel resources that can take over, share load, or provide alternate paths if the primary component becomes unavailable. It is used in network design, cloud platforms, industrial control systems, telecom infrastructure, power systems, and other high-availability environments. Constraints include cost, synchronization, state replication, testing complexity, and the fact that redundancy must be designed at the correct failure domain. Failure modes include split-brain conditions, failed failover, stale backup state, misconfigured standby roles, and redundant components that share a common hidden dependency. Tradeoffs involve higher availability versus higher cost, improved resilience versus more operational complexity, and faster recovery versus increased system overhead. Redundancy matters because resilient systems require deliberate planning for component or path failure rather than assuming perfect uptime. Cross-industry relevance is very high because all critical systems need some form of redundancy to tolerate faults and maintain service.