Design multi-region banking data synchronization
System Design: Global Bank with Multi-Region Data Consistency
A digital bank operates in multiple geographic regions (e.g., EU, US, APAC). Users can log in and perform operations (balance checks, transfers, card payments) from anywhere.
Prompt
Design a data architecture that keeps customer/account data consistent across regions.
Requirements
- High availability and low latency for reads (users worldwide).
- Correctness for money movement (no double-spend).
- Tolerate regional failures and network partitions.
- Clear consistency model: what must be strongly consistent vs what can be eventually consistent.
Discussion Points
- Replication strategy (sync/async, leader-based vs multi-leader).
- How to handle cross-region writes (especially transfers).
- Conflict resolution and idempotency.
- Operational concerns: recovery, reconciliation, auditing, observability.
AI interview prep
Core dilemma
Balancing the absolute necessity of strong consistency for financial transactions (no double-spend) with the demands for high availability and low latency across globally distributed regions, while also ensuring resilience against regional failures and network partitions.
3 tradeoffs and 3 stress tests locked
Interview prep
Unlock the interviewer X-Ray rubric, tradeoff matrix, stress tests, clarifying questions, and key concepts.
Design multi-region banking data synchronization
System Design: Global Bank with Multi-Region Data Consistency
A digital bank operates in multiple geographic regions (e.g., EU, US, APAC). Users can log in and perform operations (balance checks, transfers, card payments) from anywhere.
Prompt
Design a data architecture that keeps customer/account data consistent across regions.
Requirements
- High availability and low latency for reads (users worldwide).
- Correctness for money movement (no double-spend).
- Tolerate regional failures and network partitions.
- Clear consistency model: what must be strongly consistent vs what can be eventually consistent.
Discussion Points
- Replication strategy (sync/async, leader-based vs multi-leader).
- How to handle cross-region writes (especially transfers).
- Conflict resolution and idempotency.
- Operational concerns: recovery, reconciliation, auditing, observability.