Distributed Databases & CAP
Sharding, replication, and the theorem that says you cannot have everything.
0 of 21 answered
Start here
Copies or slices
Foundation
- Not triedCopies or slicesFoundation
- Not triedOne shard doing all the workFoundation
- Not triedThe comment that disappearedFoundation
- Not triedWhat read replicas do not fixFoundation
- Not triedWhy split a database at allFoundation
- Not triedChoosing a shard keyCore
- Not triedThe retry that charged twiceCore
- Not triedWhat synchronous replication costsCore
- Not triedA transaction across servicesChallenge
- Not triedAdding a ninth shardChallenge
- Not triedChoosing what to shard onChallenge
- Not triedOrdering events across machinesChallenge
- Not triedQuorum arithmeticChallenge
- Not triedThe coordinator that diedChallenge
- Not triedThe join across machinesChallenge
- Not triedThe row that is not there yetChallenge
- Not triedTwo primariesChallenge
- Not triedTwo writes, no orderChallenge
- Not triedWhat CAP actually forcesChallenge
- Not triedWhat CAP actually forces you to chooseChallenge
- Not triedWhy the ring uses virtual nodesChallenge