NoSQL Data Modeling for Front-end Developers
summary
Explains concrete rules: model for your queries, not your tables, with MongoDB document patterns and the extended reference pattern that stores minimal denormalized fields to avoid extra lookups. Shows when embedding wins (one‑to‑few), when referencing is required (one‑to‑zillions, avoid the 16 megabytes limit), and how to resolve joins with $lookup. Demonstrates handling duplication and staleness via batching and change streams and gives measurable tradeoffs for performance and complexity.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:05Agenda
- 1:58Database Types
- 4:45Relationships
- 5:26Embedding and Referencing
- 7:13Pros and Cons
- 8:16Cardinality
- 12:49Middleground
- 18:27Duplication
- 21:30Batch Updates
- 22:51Summary
related talks
45mNoSQL Data Modeling for Front-end Developers
44mThe Developer's Guide to Data Modelling with Document Databases
36mMongoDB Schema Design - best practices
30mHelp! I Need To UnSQLize My Application
46mFrom Tables to Documents -- Changing Your Database Mindset
55mData Modeling in a Non-Relational World
18mFrom SQL to NOSQL - a gentle intro for Devs
18mGermany's Next Top Data Model