Loading content
Redundancy is the deliberate provisioning of additional components or capacity to tolerate failures and increase availability. It includes active and passive replication, geographic distribution, and failover strategies; granularity and placement affect cost, consistency, and recovery time. Planning, monitoring, and regular testing are essential to ensure ef…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Redundancy keeps additional components, data, or paths available so a system can survive a failure or continue operating.
Redundancy grew from reliability and safety engineering, where critical functions are protected against single faults. Computing applied the principle to hardware, networks, replicated data, and operational processes.
Picture a road with an independent diversion: when one route fails, the service can remain reachable. Replicas, spare instances, and separate power or network paths play that role. Redundancy needs detection, failover, and synchronization; extra parts add cost and can hide shared failure modes.
A second instance, copy, or route takes over after a fault.
Redundant parts help only when they do not share the same failure source.
Monitoring and failover move operation to the available resource.
Redundancy matters when downtime, data loss, or safety impact must be limited. It does not replace backups or testing; replication faults, split brain, and shared dependencies require separate controls.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.