Relational Databases Don't call it a comeback!
summary
Argues that relational databases modernize rather than lose relevance by adding columnar storage for analytics (example: averaging one billion rows reads 200 GB in row format versus about 4 GB if the column is 4 bytes), native JSON/semi structured support, cross‑engine queries for combined OLTP and analytics, HTAP real‑time analytics, and distributed SQL using consensus protocols to shard across nodes while preserving ACID and enabling cloud elasticity and cost savings. MariaDB and similar systems are cited as implementing these features.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:41Who is this guy?
- 1:31How did this...
- 3:31Early Databases
- 5:24Relational Databases
- 8:51SQL Statements
- 10:58Database Management Systems
- 13:19Scaling: Vertically
- 14:32Scaling: Horizontally
- 15:55NoSQL Data Models
- 18:07NoSQL Purpose
- 19:58The Data Revolution
- 21:29Supporting Semi-Structured Data
- 23:14Columnar Storage & Real-Time Analytics
- 24:27Hybrid Transactional/Analytical Processing
- 25:15Distributed SQL
related talks
28mThe Next Decade in Data Management
01h 20mProblems with Relational Databases in 2020
02h 42mSQL (The Return): Demystifying Preconceptions and Using the DB Effectively
38mNoSQL’s biggest secret SQL never went away
47mRethinking Relational Database CRUD Design Patterns Since We Live in a Big Data World
56mNewSQL: SQL Is Here to Stay
29mBuilding on Strengths, Learning from Differences
29mModern Database Architecture: From SQL to NoSQL & Distributed SQL