Transitioning from Multi-Region to a mirrored US-East (2 AZ) topology. The objective: Maximize High Availability while eliminating "Cold Path" failure risks.
Consolidation: Moving all workloads to one region to reduce cost and complexity.
The Conflict: Party_A prefers Active/Passive (fear of locking). Party_B prefers Active/Warm (fear of silent failure).
The Goal: Prove that Multi-AZ Active/Active is safe and superior.
A mirrored stack across two Availability Zones. Use the toggles to visualize traffic flow.
Select a traffic strategy to analyze the operational impact.
The fear of database locking is inherited from Multi-Region architectures where latency is high. In a Single-Region Multi-AZ setup, the physics change completely.
Latency between AZs is < 2ms. To Redis and Mongo, this looks like a local LAN. Consensus protocols (Raft/Paxos) handle this transparently.
MongoDB uses Primary/Secondary election. Even in Active/Active, apps write to the *same* Primary. Redis uses CRDTs (Active-Active) to merge writes mathematically.
Lower latency = Lower risk of sync issues.