RPO Zero: Synchronous Replication
You'll learn: How to achieve zero data loss with synchronous replication and understand the performance costs involved.
What Is RPO Zero?
RPO Zero means that your Recovery Point Objective is literally zero — you cannot afford to lose any data, not even one millisecond's worth of writes. When a disaster strikes, you must be able to recover with 100% of committed transactions intact.
Achieving RPO Zero with Synchronous Replication
The only way to guarantee RPO zero is synchronous replication: every write must be committed to multiple geographically distributed replicas before acknowledging success to the client.
Here's how it works:
- Client sends a write request
- Primary datacenter receives the write
- Primary immediately replicates to secondary region(s)
- Primary waits for acknowledgment from secondary
- Only then does primary confirm success to client
Think of it like a bank vault that requires two keys held in different cities. You can't complete the transaction until both vaults confirm they've locked away your deposit.
The Performance Penalty
Synchronous replication introduces significant latency. If your primary is in Virginia and your secondary is in Ireland, you're adding ~80-100ms of network round-trip time to every single write operation.
This latency:
- Slows down all write-heavy workloads
- Reduces overall throughput
- Can timeout impatient clients
- Increases infrastructure costs (more connection pooling, more servers to handle slower ops)
When to Accept This Cost
Choose RPO zero when:
- Regulatory compliance demands zero data loss (financial transactions, medical records)
- The cost of losing data far exceeds performance costs
- Write volume is low enough that latency is tolerable
Key Takeaway: RPO zero via synchronous replication guarantees no data loss but forces you to pay the latency price of cross-region network round trips on every write — choose it only when data integrity is absolutely non-negotiable.