MongoDB Schema Design - best practices
summary
Covers concrete MongoDB schema choices: use embedded documents to serve common queries with one fast, atomic read and avoid joins, or use references when documents risk the 16 megabyte document limit or when subdata is rarely needed. Rules given: favor embedding unless you can justify referencing, avoid unbounded arrays (use reverse references for logs a “one‑to‑squillions” pattern), and prefer referencing for one‑to‑many or many‑to‑many to control size and cost. Mentions MongoDB University M001/M320.
AI-written summary · about
chapters (11)
- 0:00Introduction to schema design
- 2:18Relational vs MongoDB schemas
- 5:35Schema design fundamentals
- 9:04Embedding vs referencing
- 15:00One-to-one and one-to-few
- 18:07One-to-many trade-offs
- 21:16One-to-squillions
- 24:30Many-to-many relationships
- 28:42Schema design rules
- 30:07Relational vs MongoDB recap
- 33:19Resources and next steps
related talks
26mNoSQL Data Modeling for Front-end Developers
45mNoSQL Data Modeling for Front-end Developers
33mMongoDB Rules
30mHelp! I Need To UnSQLize My Application
44mThe Developer's Guide to Data Modelling with Document Databases
47mSchema design for fast applications
28mMongoDB Patterns and Anti-Patterns
01h 00mThe Modern Database Debate: Documents, Tables, or Documents in Tables?