Single Leader With Cross-Region Replicas Versus Multi-Leader (Active-Active)
TradeoffSeniorStaffUpdated
Write-heavy app deployed to two regions for low-latency writes in both.
Short answer: Multi-leader (active-active). Single leader forces one region's writes to cross-region, defeating the latency goal.
The Two Options
A
Single leader with cross-region replicas
B
Multi-leader (active-active)
Drill This: Your Pick First
The Better Pick
Option B
Multi-leader (active-active)
Single leader forces one region's writes to cross-region, defeating the latency goal. Multi-leader allows local writes; you accept conflict resolution complexity.
When the Other One Wins
Single leader with cross-region replicas
If consistency outweighs latency (e.g., financial ledger), keep single leader and accept the cross-region write hit.