Data Replication for DR
You'll learn: How to choose the right replication mode for disaster recovery based on your acceptable data loss window and geographic constraints.
The Core Tradeoff
When designing disaster recovery, data replication determines how much data you can afford to lose (your RPO) and how far apart your data centers can be while maintaining that guarantee.
Think of it like backing up your phone: syncing every photo immediately (synchronous) is safest but drains battery and requires constant connectivity, while syncing overnight (asynchronous) is efficient but risks losing a day's photos if your phone breaks.
Choosing Your Replication Mode
Synchronous Replication
- Best for: RPO near zero (≤ seconds of acceptable data loss)
- Distance constraint: Typically ≤ 100 km due to latency
- Tradeoff: Writes block until DR site confirms; higher latency, guaranteed durability
- Use case: Financial transactions, critical medical records
Asynchronous Replication
- Best for: Relaxed RPO (minutes to hours)
- Distance constraint: Unlimited—works across continents
- Tradeoff: Fast writes, but gap between primary and DR site creates data loss risk
- Use case: Analytics data, media files, non-critical applications
Semi-Synchronous Replication
- Best for: Balanced RPO (seconds to low minutes)
- Distance constraint: Medium (100-500 km)
- Tradeoff: Wait for at least one DR site acknowledgment; middle ground on durability and performance
- Use case: E-commerce systems, user-generated content
Decision Framework
Match your RPO requirement to replication mode, then verify distance works with latency constraints. If synchronous replication's latency hurts user experience but you need low RPO, consider semi-synchronous or investing in closer DR sites.
Key Takeaway: Choose synchronous replication for strict RPO requirements within latency-tolerant distances, asynchronous for flexibility across any distance with relaxed RPO, and semi-synchronous as the practical middle ground for most production systems.