Jay vemula

“In a RDBMS, since all the column names and types are defined at the table level, this information does not need to be replicated in each row. MongoDB, by contrast, doesn’t know, at the collection level, what fields are present in each document, nor does it know their types, so this information must be stored on a per-document basis.”
― Rick Copeland, MongoDB Applied Design Patterns

“The fewer documents in RAM, the more likely the server is to page fault to retrieve documents, and ultimately page faults lead to random disk I/O.”
― Rick Copeland, MongoDB Applied Design Patterns

“larger”
― Rick Copeland, MongoDB Applied Design Patterns

“The constraints of a toolset help to define patterns for solving problems. In the case of MongoDB, one of those constraints is the lack of atomic multidocument update operations. The patterns we use in MongoDB to mitigate the lack of atomic multidocument update operations include document embedding and complex updates for basic operations, with optimistic update with compensation available for when we really need a two-phase commit protocol. When designing your application to use MongoDB, more than in relational databases, you must keep in mind which updates you need to be atomic and design your schema appropriately.”
― Rick Copeland, MongoDB Applied Design Patterns