CockroachDB × SumUp
CockroachDB x SumUp: Zero-downtime migration of a 1B-transaction payments platform
Zero downtime, zero data loss migration
Legacy fragility to always-on global platform
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 story earns its Resilience tag by centering on a high-stakes live migration where the primary win was nothing bad happening: zero downtime, zero data loss, zero rollback. The mechanism is unusually specific, detailing the migration proxy, dual-write via Kafka, and UUID-based routing, giving engineers a real mental model to borrow. The New Capability angle is real too, since horizontal multi-region writes were genuinely impossible on the old stack, making this a close call between Resilience and New Capability, but the framing and metrics-first header lead with survival, not new reach.
Steal this
The three-zero scorecard ('zero downtime, zero data loss, zero rollback horror story') as a headline result frame: it converts absence-of-disaster into a concrete, memorable outcome that readers can immediately grasp and compare against their own migration fears.
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.