Record Detail Back
MongoDB Applied Design Patterns
- Share to:
When building a new application, often one of the first things you’ll want to do is to design its data model. In relational databases such as MySQL, this step is formalized in the process of normalization, focused on removing redundancy from a set of tables. MongoDB, unlike relational databases, stores its data in structured documents rather than the fixed tables required in relational databases. For instance, relational tables typically require each row-column intersection to contain a single, scalar value. Mon‐ goDB BSON documents allow for more complex structure by supporting arrays of val‐ ues (where each array itself may be composed of multiple subdocuments). This chapter explores one of the options that MongoDB’s rich document model leaves open to you: the question of whether you should embed related objects within one another or reference them by ID. Here, you’ll learn how to weigh performance, flexibility, and complexity against one another as you make this decision.
Rick Copeland - Personal Name
978-1-449-34004-9
NONE
Information Technology
English
1-175
LOADING LIST...
LOADING LIST...