MODULE 13 · 2 LESSONS
Choose document storage for access-pattern reasons, not as a default replacement for relational data.
Project checkpoint: Model an activity feed and compare embedded and referenced designs.
13of 34
Module 13 learning loop
- 1Documents
- 2Collections
- 3Embedding
- 4References
What this module changes in your work
- Decide what to embed or reference based on how the application reads and changes data.
- Apply schema validation and targeted indexes even in a flexible document model.
- Use documents, collections, embedding in one coherent implementation.
- Complete this evidence-backed checkpoint: Model an activity feed and compare embedded and referenced designs.
Lessons
Document Modeling by Access Pattern
Decide what to embed or reference based on how the application reads and changes data.
MongoDB CRUD, Validation and Indexes
Apply schema validation and targeted indexes even in a flexible document model.
PROJECT CHECKPOINT
Turn nosql and mongodb into evidence
Model an activity feed and compare embedded and referenced designs.
- Write acceptance criteria for documents before implementation.
- Keep the change small enough that a reviewer can connect it to the intended behavior.
- Use the most direct check available for collections and save the result.
- Record one decision you would keep and one you would revisit after feedback.
Share this page
Share this page with the people who will use it next.
Discussion
No comments yet. Add the first useful question or observation.
You must log in to post a comment.