From Tables to Documents -- Changing Your Database Mindset
summary
Compares SQL vs document modeling with live examples: users Leslie, Ron and Lauren modeled in MySQL and MongoDB, Python code shows a 27 lines vs 2 lines practical difference when retrieving and updating profiles. Claims four concrete advantages: horizontal scaling via sharding, faster reads by avoiding joins, flexible schema for quick pivots, and faster development because JSON documents map to language objects. Demonstrates the polymorphic pattern and the rule data that is accessed together should be stored together, and cautions that multi-document transactions are rarely needed.
AI-written summary · about
chapters (26)
- 0:00Intro
- 8:18Overview
- 10:37Example
- 18:12Term Mapping
- 23:15Changing Your Database Mindset
- 23:49Scaling
- 26:00Faster Queries
- 27:17Requirements Change
- 28:45Program Faster
- 32:04MongoDB
- 32:42User Dictionaries
- 33:20Updating User Dictionaries
- 33:40Updating Users Table
- 34:39Updating Hobbies Table
- 36:26Change Your Mindset
- 36:53Embrace Document Diversity
- 39:46Normalize Data
- 40:15Price of Storage
- 40:52Cost of Software Development
- 41:49Embedding
- 42:18Transactions
- 43:22Summary
- 44:03Advantages of documents
- 44:58Conclusion
- 45:18Additional Resources
- 45:36MongoDB Atlas
related talks
41mFrom Tables to Documents - Changing Your Database Mindset
38mFrom Tables to Documents—Changing Your Database Mindset
01h 00mThe Modern Database Debate: Documents, Tables, or Documents in Tables?
42mChoosing the right database
44mThe Developer's Guide to Data Modelling with Document Databases
18mFrom SQL to NOSQL - a gentle intro for Devs
26mNoSQL Data Modeling for Front-end Developers
55mData Modeling in a Non-Relational World