How CockroachDB Survived the Cloud Database Wars
The CTO Podcast with Fexingo · 2026-06-11 · 13 min
Episode notes
Episode 44 of The CTO Podcast dives deep into how Cockroach Labs built a distributed SQL database that could survive not just server failures, but the competitive onslaught of AWS, Google, and Microsoft. Lucas walks through the key architectural decisions - the Raft consensus protocol, the geo-partitioning trick that made multi-region compliance possible, and the controversial move to make the product open-source but the enterprise features proprietary. Luna presses on how CockroachDB lost Google's internal adoption to Spanner but won over financial-services customers like JPMorgan. The episode also covers the inflection point in 2023 when CockroachDB hit $50 million in annual recurring revenue and how the team decided to prioritize horizontal scalability over SQL compatibility. Concrete numbers include the 4.5-year development cycle to GA, the 20x latency penalty for global writes before optimization, and the 99.995 percent uptime guarantee they eventually published. A behind-the-scenes note on listener support closes the episode.
More from The CTO Podcast with Fexingo
All episodes →- How Airbnb Rebuilt Search for 8 Million Listings42 / 100
- How GitLab Built a Single Codebase for One Million CI Pipelines45 / 100
- How Slack Rebuilt Its Search Index for 10 Million Daily Queries37 / 100
- How Notion Rebuilt Its Sync Engine for Offline-First
- How Notion Rebuilt Its Block Engine for Hybrid Local-Sync