10 things a developer should know about databases
summary
Covers ten concrete database rules: choose the engine to match workload (relational for joins, document stores for schemaless data, columnar for analytics) and mentions MySQL, MongoDB, ClickHouse, Redis and Kafka. Advises scaling strategies (vertical, horizontal, sharding), test on staging sized like production, minimize disk I/O because memory is much faster (SSD ~4× HDD), use indexes carefully (faster reads but slower writes and duplicated data), avoid UUID v4 as primary key, and pick charset, isolation level, and managed vs self‑managed deployments based on tradeoffs.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:47Agenda
- 4:08Scalability
- 6:16Latency times
- 10:26Choosing the correct data type (part 2)
- 13:10Character set
- 13:58Indexes (example)
- 18:39Isolation levels
- 20:05Database security
- 21:15New isn’t always "faster" or "better"
- 22:58Conclusions
- 23:32Where to continue researching?
related talks
39m10 Things Developers should know about Databases
47m17 Things Developers Need to Know About Databases
28mSmall Data: Databases in the real world
41mHow to choose the right database for your application
01h 20mProblems with Relational Databases in 2020
12mAdvanced database topics and Database 101 for Developers
44m50 Years of Choosing the Wrong Database: Lessons from History (and My Own Projects)
02h 42mSQL (The Return): Demystifying Preconceptions and Using the DB Effectively