Problem Statement
Compare asynchronous read replicas with synchronous replicas for high availability and recovery.
Explanation
Asynchronous replicas are great for read scale and reporting. They do not slow writes, but can lag. On failover you may lose recent commits equal to the lag. They suit relaxed RPO.
Synchronous replicas acknowledge commits only after a replica confirms. This reduces or eliminates data loss at the cost of higher write latency and tighter coupling. Choose per workload, per region, and document expected RPO/RTO.
Code Solution
SolutionRead Only
-- Concept: sync commit waits for replica ACK; async returns after local log flush
Practice Sets
This question appears in the following practice sets:
