Normalized data models describe relationships using references between documents. 4. Implementing Backup/Recovery Strategies. Naming convention for collectionIn order to name a collection few precautions to be taken. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc. Model One-to-One Relationships with Embedded Documents, Model One-to-Many Relationships with Embedded Documents, Model One-to-Many Relationships with Document References, Upgrade MongoDB Community to MongoDB Enterprise, Upgrade to MongoDB Enterprise (Standalone), Upgrade to MongoDB Enterprise (Replica Set), Upgrade to MongoDB Enterprise (Sharded Cluster), Causal Consistency and Read and Write Concerns, Evaluate Performance of Current Operations, Aggregation Pipeline and Sharded Collections, Model Tree Structures with Parent References, Model Tree Structures with Child References, Model Tree Structures with an Array of Ancestors, Model Tree Structures with Materialized Paths, Production Considerations (Sharded Clusters), Calculate Distance Using Spherical Geometry, Expire Data from Collections by Setting TTL, Use x.509 Certificates to Authenticate Clients, Configure MongoDB with Kerberos Authentication on Linux, Configure MongoDB with Kerberos Authentication on Windows, Configure MongoDB with Kerberos Authentication and Active Directory Authorization, Authenticate Using SASL and LDAP with ActiveDirectory, Authenticate Using SASL and LDAP with OpenLDAP, Authenticate and Authorize Users Using Active Directory via Native LDAP, Deploy Replica Set With Keyfile Authentication, Update Replica Set to Keyfile Authentication, Update Replica Set to Keyfile Authentication (No Downtime), Deploy Sharded Cluster with Keyfile Authentication, Update Sharded Cluster to Keyfile Authentication, Update Sharded Cluster to Keyfile Authentication (No Downtime), Use x.509 Certificate for Membership Authentication, Upgrade from Keyfile Authentication to x.509 Authentication, Rolling Update of x.509 Cluster Certificates that Contain New DN, Automatic Client-Side Field Level Encryption, Read/Write Support with Automatic Field Level Encryption, Explicit (Manual) Client-Side Field Level Encryption, Master Key and Data Encryption Key Management, Appendix A - OpenSSL CA Certificate for Testing, Appendix B - OpenSSL Server Certificates for Testing, Appendix C - OpenSSL Client Certificates for Testing, Change Streams Production Recommendations, Replica Sets Distributed Across Two or More Data Centers, Deploy a Replica Set for Testing and Development, Deploy a Geographically Redundant Replica Set, Perform Maintenance on Replica Set Members, Reconfigure a Replica Set with Unavailable Members, Segmenting Data by Application or Customer, Distributed Local Writes for Insert Only Workloads, Migrate a Sharded Cluster to Different Hardware, Remove Shards from an Existing Sharded Cluster, Convert a Replica Set to a Sharded Cluster, Convert a Shard Standalone to a Shard Replica Set, Upgrade to the Latest Revision of MongoDB, Workload Isolation in MongoDB Deployments, Back Up and Restore with Filesystem Snapshots, Restore a Replica Set from MongoDB Backups, Back Up a Sharded Cluster with File System Snapshots, Back Up a Sharded Cluster with Database Dumps, Schedule Backup Window for Sharded Clusters, Recover a Standalone after an Unexpected Shutdown, db.collection.initializeUnorderedBulkOp(), Client-Side Field Level Encryption Methods, Externally Sourced Configuration File Values, Configuration File Settings and Command-Line Options Mapping, Default MongoDB Read Concerns/Write Concerns, Upgrade User Authorization Data to 2.6 Format, Compatibility and Index Type Changes in MongoDB 2.4, you have “contains” relationships between entities. The Grand Scheme (or Schema ) of Things.