NoSQL Data Modeling for Front-end Developers
summary
Covers concrete NoSQL decisions: model by access patterns, not by SQL habits; uses MongoDB features like the $lookup operator and change streams to resolve joins and batch-update stale duplicates; recommends embedding for one-to-few, referencing on the many/zillions side to avoid the 16 MB document limit, and the extended reference pattern to keep queries single-round-trip while duplicating only tiny fields; explains tradeoffs, migration triggers, and MongoDB University resources.
AI-written summary · about
chapters (10)
- 0:00Start
- 6:04Non-tabular databases
- 10:10One-to-One (1-1)
- 11:40Referencing on the "one" side
- 14:44Cardinality
- 16:57One-to-Zillions
- 20:21Are you dealing with two separate logical units?
- 26:02Extended Reference pattern
- 29:59Staleness
- 35:57Thank you for joining!
related talks
26mNoSQL 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
18mFrom SQL to NOSQL - a gentle intro for Devs
46mFrom Tables to Documents -- Changing Your Database Mindset
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
01h 00mFrom Relational Databases to NoSQL