Information Technology

MongoDB Applied Design Patterns

---

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.

---

Availability

No copy data

Detail Information

Series Title

-

Call Number

-

Publisher

: .,

Collation

1-175

Language

English

ISBN/ISSN

978-1-449-34004-9

Classification

NONE

Content Type

-

Media Type

-

Carrier Type

-

Edition

-

Subject(s)

MongoDB Applied Design Patterns

Specific Detail Info

-

Statement of Responsibility

-

Other version/related

File Attachment

Comments

---

You must be logged in to post a comment