Disaster Recovery Patterns Infographic
Cloud Architecture Guide

Disaster Recovery Patterns

Choosing the right balance between Cost, Recovery Time (RTO), and Recovery Point (RPO).

The DR Ingredients

Data Replication

The continuous or periodic copying of data from the primary site to a secondary region to ensure consistency.

Infrastructure Provisioning

Automated scripts (IaC) that can spin up servers, load balancers, and networking components on demand.

DNS/Traffic Failover

The mechanism (like Route53) that detects failure and reroutes user requests to the healthy secondary site.

Strategic Visual Comparison

How resources are distributed across Primary and Secondary regions.

Option 01

Pilot Light

“Keep the core burning, spark the rest when needed.”

  • Low Maintenance Cost
  • RTO: Tens of Minutes
  • DB is live; App is off
PRIMARY (ACTIVE) DATA SYNC SECONDARY (IDLE) INFRA OFF
Option 02

Warm Standby

“A scaled-down version ready to take the heat.”

  • Medium Cost
  • RTO: Minutes
  • Functional but Scaled Down
Small Footprint
Option 03

Active-Active

“Zero downtime, zero compromise, double the power.”

  • High Cost
  • RTO: Near Zero
  • Traffic split across regions

Key Takeaways

The choice between these patterns is rarely about technology alone—it’s about the business cost of downtime versus the infrastructure budget.

Low Tier

Pilot Light

COST EFFICIENCY

Mid Tier

Warm Standby

RECOVERY SPEED

Elite Tier

Active-Active

AVAILABILITY

© 2023 Cloud Visualization Series • Architectural Design Patterns

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top