The Distributed SQL Database Behind Twitter
summary
Claims that distributed SQL is a new architecture, not just NewSQL with tweaks: YugabyteDB reimplements storage inspired by Google Spanner, exposes a Postgres-compatible API, and provides automatic distribution of data with auto-sharding, rebalancing and active‑active replication. It promises fully ACID compliant transactions, linear horizontal scaling and Kubernetes/cloud portability. Market signals cited: ~58% of enterprises using or planning globally distributed databases and a $50–60B core DB market; a demo shows near‑instant reads across AWS and Equinix, indicating the design works.
AI-written summary · about
chapters (5)
- 0:00Introduction and context
- 4:32The case for modernization
- 9:56New SQL vs distributed SQL
- 17:34Distributed SQL characteristics
- 21:03Use cases and conclusion
related talks
47mAnatomy of a Distributed SQL Database - YugabyteDB
27mIntroduction to YugabyteDB – Design and Architecture
03mRecap and Highlights
49mPostgreSQL’s Journey to Distributed Databases
30mThe Distributed Database Behind Twitter
51mYandex Database: Distributed Queries in the Clouds
24mFailure is Not an Option: Highly Available Distributed SQL
20mThe Future of Databases