17 Things Developers Need to Know About Databases
summary
Seventeen concrete items list practical claims and tools: MySQL single-threaded queries limit single-query CPU scaling while Postgres parallel query can use multiple cores; use explain plan output and visualizers to find why a query is 1,000× slower at scale; Percona PMM-style monitoring surfaces top offenders; indexes speed reads but increase write cost and cache pressure; open transactions and missing capacity planning break backups; connection pooling or queuing enforces optimal concurrency.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:58Operations
- 4:52Devs vs Ops Conflict
- 6:38Database Responsibility
- 7:30Learn Database Basics
- 8:31Example of Relational Database Schema
- 9:01Query Execution Diagram
- 10:35EXPLAIN
- 14:37How are Queries Executed ?
- 16:53Indexes
- 20:04Capacity Planning
- 23:20Vertical and Horizontal Scaling
- 24:33Scalable = Efficient
- 27:37Speed of Light Limitations
- 30:59ORM (Object Relational Mapping)
- 32:23Understanding Optimal Concurrency
- 34:23Benefits of Connection Pooling
- 35:20Law of Gravity
- 35:49Scale Matters
- 37:19Newer is not Always Faster
- 37:55Upgrades are needed but not seamless
- 38:53Character Sets
- 40:25Operational Overhead
- 41:33Risks of Automation
- 44:56Open Source Database Survey
related talks
39m10 Things Developers should know about Databases
35m10 things a developer should know about databases
12mAdvanced database topics and Database 101 for Developers
49m18 Ways to Fix MySQL Bottlenecks
18mPower Hour, Managing Databases at Scale – Peter Zaitsev
25mMySQL Performance for DevOps
23mFANTASTIC DATABASES AND WHERE TO FIND THEM
53mMySQL DevOps