The official ten-year retrospective of NewSQL databases
summary
Term "NewSQL" originates 2011 and means relational + ACID for scalable OLTP, aiming to combine SQL transactions with NoSQL scale. Implementations split into new architectures (VoltDB, Spanner), middleware (Citus → Microsoft), and DBaaS; many startups (Xeround, GenieDB, TransLattice) fold while MemSQL becomes SingleStore. Cloud adoption and mature Postgres/MySQL make market entry hard. Market language shifts to distributed SQL, practitioners add transactions to NoSQL products, and future wins hinge on automation and cloud-native operation rather than redoing SQL.
AI-written summary · about
chapters (16)
- 0:00Start
- 4:21Scalability
- 6:19Three Key Questions
- 11:57Nosql Systems
- 14:13Key Value Stores
- 14:48Mongodb
- 17:34Rise of the New Sql Systems
- 24:11New Database System Architecture
- 27:20Middleware
- 28:44Vendors
- 29:17Database as a Service
- 30:36Mysql Storage Engines
- 43:25Existing Open Source Database Systems
- 44:52The Cloud Changes Everything
- 51:33Distributed Sql
- 1:00:17Branding
related talks
12mNewSQL Leveraging PostgreSQL
56mNewSQL: SQL Is Here to Stay
26mNewSQL: concepts, realities and when you should embrace it
43mThe State of NoSQL in 2021
31mSQL to NoSQL to NewSQL and the rise of polyglot persistence Paul Dix
38mNoSQL’s biggest secret SQL never went away
29mModern Database Architecture: From SQL to NoSQL & Distributed SQL
45mDemystifying NoSQL: The SQL developer's guide