1. Problem Statement
Design a distributed Key-Value store that prioritizes Write Availability above everything else. E.g. the Amazon Shopping Cart service. It must never reject a write.
2. Architecture Discussion Map
Use this as one discussion aid, not a single correct answer. Your design should follow from the requirements, scale, and trade-offs you establish.
Rendering architecture diagram...
Mermaid Source (For AI Bots)
graph LR
A["Design Amazon DynamoDB"]
A --> F1["Partitioning Consistent Hashing"]
A --> F2["High Availability Leaderless Replication / Multi-master"]
A --> F3["Consistency Quorum reads/writes, W+R > N"]
A --> F4["Conflict Resolution Vector Clocks, Last-Write-Wins"]
A --> F5["Failure Detection Gossip Protocol"]3. Key Focus Areas
- 1Partitioning (Consistent Hashing)
- 2High Availability (Leaderless Replication / Multi-master)
- 3Consistency (Quorum reads/writes, W+R > N)
- 4Conflict Resolution (Vector Clocks, Last-Write-Wins)
- 5Failure Detection (Gossip Protocol)
Want interactive feedback?
Practice drawing this system component-by-component on a live whiteboard while the interviewer probes at your target level.
Continue to DashboardCore Concepts
System DesignDistributed DatabasesConsistency
