Spanner - fully managed horizontally scalable relational DB with ACID transactions
summary
Spanner is a fully managed, horizontally scalable relational database that gives global strong consistency by combining PAXOS replication with TrueTime (GPS and atomic clocks) and separates compute from storage so nodes can be added quickly. The demo is a ticket-sales schema with counters, secondary indexes and a 2 billion row / 30 TB ticket table; rebalancing takes 10–30 seconds. Transactions use mutations with limits of 20,000 mutations and a ~1MB sweet spot. Live coding shows no-downtime schema changes, Java/Go/Python clients and a Spring Data integration.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:03What we needed
- 3:01What is Spanner
- 4:30Spanner for Cloud
- 5:22Spanner vs Traditional DB
- 8:32Spanner use cases
- 10:13How Spanner works
- 15:15Epsilon
- 15:56GPS
- 17:05Consistency
- 19:55ReadWrite
- 21:25Relational Model
- 21:55One Edition
- 23:52Writing
- 24:22Antipatterns
- 25:33Schema design
- 27:51Demo
- 33:13Life Coding
- 33:27Java
- 40:50Readonly code
- 45:28Deletes
- 46:03Spring Boot Integration
related talks
41mSpanner - Google's Distributed Database
22mOrder And Consistency At Scale
33mGoogle Cloud Spanner: Global consistency at scale
47mGoogle Cloud Spanner: Global consistency at scale
01h 08mKeynote: Building Spanner
37mGoogle Cloud Spanner: Going global with relational database
12mSpanDB: A Fast, Cost-Effective LSM-tree Based KV Store on Hybrid Storage
49mPostgreSQL’s Journey to Distributed Databases