$lookup for joining collections in MongoDB - Time & Space Complexity
When using $lookup in MongoDB, we want to know how the time it takes grows as the data grows.
We ask: How does joining two collections affect the work the database does?
Analyze the time complexity of the following code snippet.
db.orders.aggregate([
{
$lookup: {
from: "products",
localField: "product_id",
foreignField: "_id",
as: "product_details"
}
}
])
This code joins the orders collection with the products collection to add product details to each order.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: For each order document, MongoDB searches the
productscollection for matching_id. - How many times: Once per order document, so the number of orders times the cost to find matching products.
Explain the growth pattern intuitively.
| Input Size (orders) | Approx. Operations |
|---|---|
| 10 | About 10 lookups in products |
| 100 | About 100 lookups in products |
| 1000 | About 1000 lookups in products |
Pattern observation: The work grows roughly in direct proportion to the number of orders.
Time Complexity: O(n)
This means the time grows linearly with the number of documents in the main collection.
[X] Wrong: "The join time depends only on the size of the joined collection."
[OK] Correct: The join time depends mainly on how many documents you process in the main collection, because each triggers a lookup.
Understanding how $lookup scales helps you explain database joins clearly and shows you can think about performance in real projects.
"What if the foreignField is indexed? How would the time complexity change?"
Practice
$lookup stage do in a MongoDB aggregation pipeline?Solution
Step 1: Understand the purpose of
$lookup$lookupis used to combine documents from two collections by matching fields.Step 2: Compare with other options
Deleting, sorting, or updating documents are different operations and not related to$lookup.Final Answer:
It joins documents from two collections based on a matching field. -> Option BQuick Check:
$lookupjoins collections = A [OK]
- Confusing $lookup with update or delete operations
- Thinking $lookup sorts documents
- Assuming $lookup modifies documents instead of joining
$lookup stage in MongoDB?Solution
Step 1: Identify correct field names in $lookup
The correct keys arefrom,localField,foreignField, andas.Step 2: Check each option
{ $lookup: { from: 'other', localField: 'id', foreignField: 'userId', as: 'joinedData' } } uses all correct keys and syntax. Options A, B, and C have incorrect or missing keys.Final Answer:
{ $lookup: { from: 'other', localField: 'id', foreignField: 'userId', as: 'joinedData' } } -> Option CQuick Check:
Correct $lookup keys = D [OK]
- Using wrong key names like collection or joinAs
- Omitting the 'as' field for output array
- Missing foreignField or localField keys
orders with documents { _id: 1, productId: 101 } and products with documents { _id: 101, name: 'Pen' }, what will be the result of this aggregation on orders?
{ $lookup: { from: 'products', localField: 'productId', foreignField: '_id', as: 'productInfo' } }Solution
Step 1: Match localField and foreignField values
TheproductIdinordersis 101, which matches_id101 inproducts.Step 2: Understand $lookup output
The matching product document is added as an array inproductInfo.Final Answer:
[{ _id: 1, productId: 101, productInfo: [{ _id: 101, name: 'Pen' }] }] -> Option AQuick Check:
Matching product added in array = B [OK]
- Expecting productInfo to be a single object, not an array
- Thinking no match means error instead of empty array
- Ignoring the 'as' field name in output
$lookup stage?
{ $lookup: { from: 'users', localField: 'userId', foreignField: 'id', as: 'userDetails' } }
Assuming the users collection uses _id as the user ID field.Solution
Step 1: Check foreignField correctness
Theuserscollection uses_idas the ID field, soforeignFieldmust be '_id'.Step 2: Verify other fields
localFieldandasare valid; collection name 'users' is correct.Final Answer:
The foreignField should be '_id' instead of 'id'. -> Option DQuick Check:
foreignField must match actual field = C [OK]
- Using wrong foreignField name
- Changing 'as' field unnecessarily
- Mistaking collection name pluralization
students with { _id: 1, name: 'Alice' } and grades with multiple documents per student like { studentId: 1, score: 85 }. How do you write a $lookup to get each student with all their grades in an array called allGrades?Solution
Step 1: Identify matching fields between collections
students._idmatchesgrades.studentId, so these are the fields to join on.Step 2: Write $lookup with correct fields and output array name
Usefrom: 'grades',localField: '_id',foreignField: 'studentId', andas: 'allGrades'.Final Answer:
{ $lookup: { from: 'grades', localField: '_id', foreignField: 'studentId', as: 'allGrades' } } -> Option AQuick Check:
Match student _id to grades studentId = A [OK]
- Swapping localField and foreignField
- Using wrong fields like name or score for join
- Incorrect output array name
Ready to prove it?
Pass the test and this pattern moves unknown
