N+1 and N+2 Redundancy
You'll learn: How to provision extra capacity beyond the bare minimum so your system stays healthy even when components fail.
The Core Idea
N+1 redundancy means if you need N components to handle your workload, you provision N+1 — one extra. If any single component fails, the remaining N can still carry the full load.
N+2 redundancy takes it further: you provision N+2 components, surviving up to two simultaneous failures.
Think of it like chairs at a dinner party. If you expect 10 guests (N=10) and have exactly 10 chairs, one broken chair ruins someone's evening. With N+1 (11 chairs), one failure is fine. With N+2 (12 chairs), you can lose two chairs and still seat everyone comfortably.
When to Use Each
- N+1: Standard practice for most production systems. Protects against single component failures (servers, power supplies, network links).
- N+2: Critical systems where even brief degradation is unacceptable, or where maintenance windows require taking components offline without impacting capacity.
Real-World Example
If your application needs 4 servers to handle peak traffic:
- Bare minimum: 4 servers (risky!)
- N+1: 5 servers (survives 1 failure)
- N+2: 6 servers (survives 2 failures)
The extra capacity isn't wasted — it provides headroom for traffic spikes, maintenance, and deployments.
Cost vs Risk Tradeoff
Higher redundancy = higher infrastructure cost but lower availability risk. Your choice depends on SLAs, error budgets, and the business impact of downtime.
Key Takeaway: N+1 redundancy provisions one extra component beyond minimum requirements; N+2 provisions two, each offering progressively better fault tolerance at higher cost.