the future of distributed SQL
summary
Companies push CockroachDB to add concrete features: a seven‑region data locality topology for US sports betting; a survival goal abstraction that cuts hundreds of config lines to a few SQL commands; a zero‑downtime migration using cross‑cluster restore plus CDC to avoid a 20‑minute outage for CMK encryption; serverless multi‑region with per‑tenant PrivateLink; 800 change feeds, 40 features in six months, and measured 5x performance and linear scale from 20 to 200 nodes.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 0:44"The customer perspective is in our DNA"
- 7:35Market-shaping companies using CockroachDB
- 9:42The commitment to partnership at Cockroach Labs
- 13:56How an online betting company helped us bring Data Locality to CockroachDB
- 17:06How an access management company helped us bring Survival Goals to CockroachDB
- 18:41How an identity infrastructure company helped us bring migrations to CockroachDB
- 20:59How a data loss prevention company helped us bring Serverless multi-region to CockroachDB
- 23:00How a finserv company helped us bring failure testing, training, & feature velocity to CockroachDB
- 27:00How an on-demand delivery company helped us bring Change Data Capture (CDC) to CockroachDB
- 29:56How an online game platform helped us improve performance and scalability features in CockroachDB
- 31:01Why partnerships are the key to success + closing remarks
related talks
31mFuture-proofing operational data at scale
48mBuilding mission-critical applications with CockroachDB
24mNavigating Distributed Databases: Challenges & Opportunities
15mScaling to support America’s #1 sportsbook
14mHow CockroachDB can enable Multi-Region Deployments and Data Locality 
52mCockroachDB
42mThe hows and whys of a distributed SQL database
15mScaling to support America’s #1 sportsbook