Impact of Global Network Latency on Strong Consistency and RTO/RPO Metrics
Updated Apr 28, 2026
Short answer
Strong consistency requires synchronous commits across regions, meaning write latency is equal to the round-trip time between the two farthest replicas.
Deep explanation
In a globally distributed setup, Strong consistency is bound by the speed of light. To guarantee that a read always returns the latest write, the write must be acknowledged by a majority of replicas worldwide before the client gets a success. This effectively caps your write latency at the network RTT (e.g., 200ms between London and Sydney). This drastically impacts RPO (Recovery Point Objective), which becomes 0, but negatively affects availability during network partitions.
Unlock with a Pro subscription to view this section.
View pricingReal-world example
No real-world example available yet.
Unlock with a Pro subscription to view this section.
Upgrade to ProCommon mistakes
No common mistakes listed yet.
Unlock with a Pro subscription to view this section.
Upgrade to ProFollow-up questions
No follow-up questions available yet.
Unlock with a Pro subscription to view this section.
Upgrade to Pro