CockroachDB × Squarespace
CockroachDB x Squarespace, zero-downtime global database migration at scale
<10ms cutovers, 100 cutovers across 50 clusters with zero downtime
Managing data silos to managing data as streams from a system of record
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 piece earns its primary tag through the five-phase migration walkthrough, which describes something Squarespace genuinely could not do before: run a globally distributed, always-on relational database across multiple regions without planned downtime windows. The mechanism is unusually specific, covering CDC via Debezium, Kafka queuing, HAProxy pivoting, and a fallback stream from CockroachDB changefeeds, giving readers a replicable blueprint. There is a coin-flip tension with Resilience, since the win is partly about surviving outages and natural disasters, but the lead framing is capability unlocked, not a bad event avoided.
Steal this
The five-phase migration checklist with explicit fallback handling (streaming CockroachDB mutations back to a separate topic post-cutover so writes are preserved if rollback is needed) is a rare structural move: it turns a case study into a migration runbook, making the piece genuinely useful to engineers evaluating the same switch.
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.