Member-only story
Mongo DB Schema Design Anti-Patterns — Part 1
Find out the don’ts while designing schema in MongoDB

Software developers love design patterns and well design patterns give us best practices in a common languages as we architect applications. When modeling data to be stored in MongoDB database we talk about Schema design patterns.
Schema design patterns help developers be successful as they plan and iterate on their designs.
But here’s the thing, some developers jump right into building their apps without thinking about making a design following best practices and without even realizing it they’ve coated themselves into a big mess.
During development, when the requirements change or my database needs to scale I just care about doing the minimum work to get something working and that’s why we at mongodb have identified six common schema design anti patterns.
The goal is to learn about and prevent schema design anti-patterns so we don’t accidentally starting to go down a dangerous path that will lead to inefficient queries.
I’m also going to assume you’re comfortable with the basics of how to store data using the document…