MongoDB Relationships Best Practices

Design a Schema for a Social Media App

Design a MongoDB schema for users and their posts, deciding when to embed and when to reference related data.

Expected output: A schema design document explaining embedding and referencing choices.

Hint: Consider how often posts and user data are accessed together and the expected size of posts.

Refactor an Existing Schema

Given a schema with excessive embedding causing large documents, refactor it to use referencing where appropriate.

Expected output: A revised schema with explanations for changes.

Hint: Identify large arrays or frequently updated embedded documents.

Embedding is preferred when related data is tightly coupled, accessed together, and the relationship is one-to-few, as it improves read performance and atomicity.

Embedding can lead to large documents that may exceed MongoDB's 16MB document size limit and can cause performance issues if the embedded arrays grow unbounded.

MongoDB does not enforce foreign keys or joins by default; relationships are managed through embedding or referencing, and consistency must be handled at the application level or via transactions.