CockroachDB × FanDuel
4x scale (approx. 5K transactions per second) with RPO of 0
Fragile, manual disaster recovery to always-on, self-healing ledger
Members read free
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.
The regulatory constraint (Wire Act compliance requiring a separate ledger per state) is a genuine structural driver that makes the architecture challenge concrete and credible. The POC section shows real benchmarking steps (9-node cluster, 5K TPS, specific schema changes) which gives the mechanism more detail than most infrastructure case studies. The story sits between Resilience and New Capability: the primary win is surviving a high-stakes migration with zero RPO and always-on guarantees, but the ability to spin up in a new state from day one is a genuinely new operational capability.
Anchor the technical narrative around a hard regulatory constraint (Wire Act, per-state deployment) rather than a generic scale story. The compliance requirement becomes the villain that makes every architectural choice feel necessary and the solution feel earned.
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.