liveBook · Manning

Redundancy

As explained in Grokking Software Architecture

Redundancy is the provision of duplicate or alternate components or resources so a system can continue operating after a failure.

Redundancy adds alternate components or resources so a system can keep operating when something fails. But a duplicate is not automatically a resilient fallback: if both paths share the same flaw, both can fail together. section 10.7.2

Two computers, one failure

Ariane 5 had a backup navigation computer, but it ran the same software as the primary. When an overflow crashed one, the other hit the same code and crashed too. A useful fallback needs a different way to respond, such as returning a cached result or gracefully degrading the experience. section 10.7.2

Design the alternate path around the failure you need to survive:

  • Use a queue to hold messages while a database is unavailable, then process them when it returns. section 7.6.5
  • Use database replicas for failover or regional reads, but keep offline backups too: destructive changes can spread to replicas. The 3-2-1 rule calls for three copies, two storage types, and one offsite or cross-region immutable copy. section 10.5.4
  • Match storage redundancy to business needs: reducing recovery time or data loss can increase cloud storage costs. section 10.5.4

How Grokking Software Architecture covers it

How deep it goes
Contrasts identical backups with diverse fallbacks, then distinguishes live replication from recoverable offline backups.
Examples
Uses Ariane 5's matching navigation computers, Apollo 13's Lunar Module, event queues, database replicas, and 3-2-1 backups.
What you can do after
Evaluate whether a backup avoids the original failure and align data copies with acceptable recovery time and data loss.
How it connects
Links resilience with fallbacks, event-driven queues, database replication, fault tolerance, and backups.

Also explained in

Compare how 13 books explain redundancy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.