CockroachDB × Booking.com
CockroachDB x Booking.com, migrating 20TB off Cassandra to simplify order management
99.999% availability across 3 regions, 20TB migrated
Cognitive overload from complex architecture to simplified, manageable system
Members read free
Unlock the full breakdown
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
Why it works
The case study earns its Efficiency tag by showing a concrete before/after architecture diagram and naming the specific technical debt removed: the locking system, OpenSearch replication, and denormalized data models all eliminated after the switch. The competitive switch from Cassandra is explicit and the technical failure modes are described with enough specificity to be credible. The story also carries a genuine Resilience thread since 99.999% availability and multi-region failover are core outcomes, making this a close call between the two types, but the framing leads with simplification and overhead reduction rather than survivability.
Steal this
The side-by-side before/after architecture diagram that makes complexity reduction visible without requiring the reader to parse paragraphs of technical explanation.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are CockroachDB's published work; we link to the source and lead with our analysis.