10 Things Developers should know about Databases
summary
Ten concrete rules: learn schema and query execution, test at scale and benchmark rather than trust vendor claims, and treat databases as a shared responsibility. Key specifics: MySQL runs a single query in one core, distributed systems like TiDB use many cores/nodes but add latency, and indexes can speed queries by 1,000x but slow inserts/updates and complicate plans. Watch for capacity limits, network speed‑of‑light latency, 50k+ connections cost, pathological pages with 70k queries, utf8mb4 for emoji, and costly backups/rebuilds.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:20Who are you
- 1:08Programming language
- 2:08DevOps
- 3:25Conflict
- 3:51Stupid Database
- 4:38Shared Responsibility
- 4:58Top Recommendations
- 5:10Database Basics
- 6:19Database Execution
- 7:07Single Thread
- 8:24Indexes
- 10:14Capacity
- 12:28Scaling
- 13:27Examples
- 14:25Tidy
- 15:14Latency
- 16:31Speed of Light
- 19:05Network Latency
- 20:53Connection Cost
- 23:15Scale and Performance
- 25:31Memory vs Disk
- 28:31Application Changes
- 29:31Character Sets
- 31:43Operational Overhead
- 32:51Distributed Systems
- 35:01Security
related talks
35m10 things a developer should know about databases
47m17 Things Developers Need to Know About Databases
01h 00m50 Things All SQL Server Developers Need to Know
12mAdvanced database topics and Database 101 for Developers
02h 42mSQL (The Return): Demystifying Preconceptions and Using the DB Effectively
28mThe Next Decade in Data Management
28mBecoming a DBA for 5 minutes a day, the most important things to know for sysadmins and developers
28mSmall Data: Databases in the real world