Course contentsShow
← Cloud and Infrastructure
Lesson 2451 of 2,98953. High Availability PatternsFree lesson

Redundancy Principles and Types

Understand active-active, active-passive, and N+1 redundancy patterns for eliminating SPOFs.

Redundancy Principles and Types

What you'll learn: How to eliminate single points of failure using active-active, active-passive, and N+1 redundancy patterns.


What is Redundancy?

Redundancy means having backup components ready to take over when a primary component fails. Think of it like having spare tires in a truck convoy—if one tire fails, you swap in a spare without stopping the journey.

The goal is simple: eliminate single points of failure (SPOFs) by ensuring no single component's failure brings down your entire system.


Three Core Redundancy Patterns

Active-Active

Both (or all) redundant components handle traffic simultaneously. If one fails, the others continue without interruption.

  • Example: Two load balancers both serving requests at the same time
  • Benefit: Maximum resource utilization and instant failover
  • Tradeoff: More complex to manage state and synchronization

Active-Passive

One component actively handles traffic while backups remain idle (standby). When the active component fails, a passive one takes over.

  • Example: Primary database server with a standby replica that only activates on failure
  • Benefit: Simpler to manage; clear roles
  • Tradeoff: Standby resources sit unused until needed

N+1 Redundancy

You need N components to handle your load, but you provision N+1 (or N+2) so at least one can fail without impact.

  • Example: If you need 4 web servers for capacity, deploy 5
  • Benefit: Balances cost with resilience
  • Tradeoff: Still vulnerable if multiple components fail simultaneously

Choosing the Right Pattern

Select based on RTO requirements, cost tolerance, and application architecture. Active-active suits stateless workloads; active-passive fits stateful databases; N+1 works well for horizontally scalable components.

Key Takeaway: Redundancy patterns—active-active, active-passive, and N+1—provide different trade-offs between cost, complexity, and resilience to eliminate single points of failure in your architecture.