Jay vemula

“By “punting” on these problems and not supporting joins or multidocument transactions at all, MongoDB has been able to implement an automatic sharding solution with much better scaling and performance characteristics than you’d normally be stuck with if you had to take relational joins and transactions into account.”
― Rick Copeland, MongoDB Applied Design Patterns

“holder, data specialist, and big-data mindset—in turn.”
― Viktor Mayer-Schönberger, Big Data: A Revolution That Will Transform How We Live, Work and Think

“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

“One final factor that weighs in favor of using document references is the case of many-to-many or M:N relationships.”
― Rick Copeland, MongoDB Applied Design Patterns