The Lost Art of Database Design
summary
Argues that concrete schema choices change cost and ops: replacing email PKs with a compact crc32 primary key shrinks indexes, a case yields 43% cost reduction; splitting historical/live separation cuts index build time from days to minutes and avoids multi‑day backups; pick tight data types (199 countries fits tiny enums), avoid blanket SELECT and excess indexes, and plan for index temp space (indexes can need twice the table) so migrations and replicas stay practical.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:22Database Design Matters
- 12:15Should I Have All the Data in the Same Database
- 17:16Create the Right Indexes
- 28:28Access Patterns
- 35:32Creation of Indexes
- 44:15The Limitations of Your Database and Infrastructure
related talks
51mThe Lost Art of Database Design
01h 02mDesign Good Schemas - Get a Better Database
28mSmall Data: Databases in the real world
31mDesigning Effective Schema for Innodb
25mThe Secret Life of SQL: How to Optimize Database Performance
11mThe Seven Principles for Making a PostgreSQL DB Work Fast
22mAdvanced HBase Schema Design
30mPerformance: Tips & Tricks to Optimize the Speed of Your Mission-Critical Database