Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Mar 11, 2012
One of the challenges that comes with moving to MongoDB is figuring how to best model your data. While most developers have internalized the rules of thumb for designing schemas for RDBMSs, these rules don't always apply to MongoDB. The simple fact that documents can represent rich, schema-free data structures means that we have a lot of viable alternatives to the standard, normalized, relational model. Not only that, MongoDB has several unique features, such as atomic updates and indexed array keys, that greatly influence the kinds of schemas that make sense. Understandably, this begets good questions:
-Are foreign keys permissible, or is it better to represent one-to-many relations within a single document? -Are join tables necessary, or is there another technique for building out many-to-many relationships? -What level of denormalization is appropriate? -How do my data modeling decisions affect the efficiency of updates and queries?
In this webcast, we'll answer these questions and more, provide a number of data modeling rules of thumb, and discuss the tradeoffs of various data modeling strategies.
About Jared Rosoff:
Jared is the Director of Product Marketing and Technical Alliances at 10gen. Before joining 10gen, Jared ran Product Development at Yottaa where he developed a real-time analytics engine on top of MongoDB and Ruby on Rails.