Embedding vs Referencing — Interview Answer — MongoDB Technical Interview Questions & Answers

Model answer covering read patterns and document growth.

Embedding vs Referencing — Interview Answer

  • Model answer: Embed when data is small and always read with the parent. Reference when it is large or shared.
  • Example: address embedded. Courses referenced. Mention 16MB.

Technical Interview Tip: Two examples. One limit.

Code Examples for Embedding vs Referencing — Interview Answer

Embedding vs Referencing — Interview Answer — working example

// Embedding (read locality):
db.orders.insertOne({
  orderId: "O-100",
  customer: { name: "Ada", email: "ada@example.com" },
  items: [{ sku: "BOOK", qty: 2, price: 399 }]
})

// Referencing (avoid unbounded growth):
db.orders.insertOne({
  orderId: "O-101",
  customerId: ObjectId("507f1f77bcf86cd799439011"),
  itemIds: [ObjectId("507f191e810c19729de860ea")]
})
// Then join when needed:
db.orders.aggregate([
  { $match: { orderId: "O-101" } },
  { $lookup: { from: "users", localField: "customerId", foreignField: "_id", as: "customer" } }
])

Embedding vs Referencing — Interview Answer — embed for data read together; reference when related data is shared or grows without bound.

How to Explain Embedding vs Referencing — Interview Answer to an Interviewer

Embed vs reference?

Inside the document vs id elsewhere