Cloud Disaster Recovery & Multi-Region Active-Active

1. What It Is & Why It Exists

The Core Problem: Regional Catastrophes & Data Loss

Cloud infrastructure is vulnerable to catastrophic failures: optical fiber cuts, undersea cable severing, regional power grid collapse, data center flooding, or rogue software deployments taking down an entire cloud region (e.g., us-east-1). To survive regional outages, systems must be engineered against two primary recovery metrics:

1. RPO (Recovery Point Objective): The maximum acceptable data loss measured in time (e.g., $0\text{ seconds}$ for financial ledgers, $15\text{ minutes}$ for analytical metrics).
2. RTO (Recovery Time Objective): The maximum acceptable downtime before the service is fully restored in a secondary region (e.g., $< 30\text{ seconds}$ for tier-1 payment gateways, $4\text{ hours}$ for internal back-office tooling).

Interactive Architecture Diagram
100%Fit100%
Synthesizing vector architecture diagram...

2. The 4 Cloud Disaster Recovery Strategies

Interactive Architecture Diagram
100%Fit100%
Synthesizing vector architecture diagram...

Comprehensive DR Comparison Matrix

3. Multi-Region Active-Active Data Synchronization & CRDTs

In Active-Active systems, writes occur simultaneously in both us-east-1 (Virginia) and eu-west-1 (Ireland). Because synchronous cross-ocean network latency is $\approx 70-100\text{ ms}$, writes must be committed locally and replicated asynchronously.

Interactive Architecture Diagram
100%Fit100%
Synthesizing vector architecture diagram...

Conflict-Free Replicated Data Types (CRDTs)

To prevent data loss in collaborative data sets (e.g., shopping carts, like counters), systems use state-based or operation-based CRDTs:

• PN-Counter (Positive-Negative Counter): Maintains two vector maps $P$ and $N$ tracking increments and decrements per region. The true value is $\sum P - \sum N$. Merges are mathematically commutative, associative, and idempotent.
• LWW-Element-Set (Last-Write-Wins Set): Adds elements with a hybrid physical-logical timestamp (HLC). Merging takes the highest timestamp.