Have a SQL and Eat it Too!
summary
A team migrates call state out of an Elixir app using Ecto to try CockroachDB as a globally distributed SQL store (three-node clusters, 64MB ranges, per-range Raft majority quorum). Migration is trivial—swap the connection URL—and ops like geo-aware leaseholder movement and single-binary deployment impress. Real measurements show ~500 ms observed tail latency under test while VoIP requirements demand <100 ms SLR, so the prototype solves availability and operational pain but fails the latency target.
AI-written summary · about
chapters (10)
- 0:00Intro
- 8:14Stateless
- 10:05Postgres
- 11:30Multicloud
- 13:19cockroach DB
- 15:25consensus protocol
- 18:39ranges
- 20:58write
- 24:51failover
- 26:22Distributed
related talks
48mBuilding mission-critical applications with CockroachDB
52mCockroachDB
24mNavigating Distributed Databases: Challenges & Opportunities
01h 11mFearless global transactions with
42mThe hows and whys of a distributed SQL database
31mFuture-proofing operational data at scale
14mBuilding CockroachDB for performance at scale
15mScaling to support America’s #1 sportsbook