Schema Design with MongoDB
Tuesday, April 27, 2010 from 1:00 PM to 2:00 PM (PDT)
One of the challenges that comes with moving to MongoDB is figuring how best to 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 relations?
- What level of denormalization is appropriate?
- How do my data modeling decisions affect the efficiency of updates and queries?
In this session, 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. There will also be plenty of time for Q & A; sign up for the session, and bring your hard questions.
Kyle Banker works at 10gen, where he maintains the MongoDB Ruby Driver and supports the Ruby developer community. Previously, Kyle built e-commerce and social networking applications at Alexander Interactive, and he once thrived as a languages nerd and a teacher of English lit.
Contact firstname.lastname@example.org for more information.
When & Where
By offering the best of traditional databases as well as the flexibility, scale and performance today’s applications require, we let innovators deploy apps as big as they can possibly dream. From startups to enterprises, for the modern and the mission-critical, MongoDB is the database for giant ideas. For more information, visit www.mongodb.com.