A Summary of Schema Design Anti-Patterns and How to Spot Them
Rate this article
Below is a brief description of each of the schema design anti-patterns we've covered in this series.
If you'd like to learn more about each of the anti-patterns, check out this YouTube playlist.
Once you have built your data modeling foundation on schema design patterns and anti-patterns, carefully consider your use case:
- What data will you need to store?
- What data is likely to be accessed together?
- What queries will be run most frequently?
- What data is likely to grow at a rapid, unbounded pace?
The great thing about MongoDB is that it has a flexible schema. You have the power to rapidly make changes to your data model when you use MongoDB. If your initial data model turns out to be not so great or your application's requirements change, you can easily update your data model. And you can make those updates without any downtime! Check out the for more details.
If and when you're ready to lock down part or all of your schema, you can add . Don't worry—the schema validation is flexible too. You can configure it to throw warnings or errors. You can also choose if the validation should apply to all documents or just documents that already pass the schema validation rules. All of this flexibility gives you the ability to validate documents with different shapes in the same collection, helping you migrate your schema from one version to the next.
Hopefully, you'll keep all of the schema design patterns and anti-patterns top-of-mind while you're planning and modifying your database schema. But maybe that's wishful thinking. We all make mistakes.
If your database is hosted on , you can get some help spotting anti-patterns. Navigate to the Performance Advisor (available in M10 clusters and above) or the Data Explorer (available in all clusters) and look for the Schema Anti-Patterns panel. These Schema Anti-Patterns panels will display a list of anti-patterns in your collections and provide pointers on how to fix the issues.
Every use case is unique, so every schema will be unique. No formula exists for determining the "right" model for your data in MongoDB.
Give yourself a solid data modeling foundation by learning the MongoDB schema design patterns and anti-patterns. Then begin modeling your data, carefully considering the details of your particular use case and leveraging the principles of the patterns and anti-patterns.
So, get pumped, have fun, and model some data!
Check out the following resources for more information: