Single document atomicity in MongoDB - Mini Project: Build & Apply

Understanding Single Document Atomicity in MongoDB

📖 Scenario: You are managing a small online store's inventory using MongoDB. You want to update the stock quantity and price of a product in a way that both changes happen together or not at all, ensuring data consistency.

🎯 Goal: Build a MongoDB update operation that modifies multiple fields of a single product document atomically.

📋 What You'll Learn

Create a collection named products with one product document having fields _id, name, stock, and price.

Define a variable product_id holding the _id of the product to update.

Write an update query that atomically changes the stock and price fields of the product with _id equal to product_id.

Ensure the update uses a single document atomic operation.

💡 Why This Matters

🌍 Real World

In real online stores, updating product stock and price together prevents errors like selling out-of-stock items or showing wrong prices.

💼 Career

Understanding single document atomicity is essential for database developers and backend engineers to maintain data consistency and reliability.

1

Create the products collection with one product document

Create a products collection and insert one document with _id set to 1, name set to 'Wireless Mouse', stock set to 50, and price set to 25.99.

MongoDB

// Insert the product document into the products collection
// Your code here

Hint

Use insertOne to add a single document to the products collection.

2

Define the product_id variable

Define a variable called product_id and set it to 1 to represent the product's _id.

MongoDB

db.products.insertOne({ _id: 1, name: 'Wireless Mouse', stock: 50, price: 25.99 })
// Define product_id variable
// Your code here

Hint

Use const product_id = 1 to store the product's ID.

3

Write an atomic update query for the product document

Write an update query using updateOne on the products collection that finds the document with _id equal to product_id and atomically updates the stock to 45 and price to 23.99.

MongoDB

db.products.insertOne({ _id: 1, name: 'Wireless Mouse', stock: 50, price: 25.99 })
const product_id = 1
// Update stock and price atomically
// Your code here

Hint

Use updateOne with a filter on _id and the $set operator to update multiple fields atomically.

4

Complete the atomic update operation

Add the option {} to the updateOne method call to complete the update operation. This confirms the update is a single atomic operation on one document.

MongoDB

db.products.insertOne({ _id: 1, name: 'Wireless Mouse', stock: 50, price: 25.99 })
const product_id = 1
db.products.updateOne({ _id: product_id }, { $set: { stock: 45, price: 23.99 } })
// Add options object to updateOne
// Your code here

Hint

Pass an empty options object {} as the third argument to updateOne to complete the call.

Practice

1. What does single document atomicity mean in MongoDB?

easy

A. All changes to a single document happen completely or not at all

B. Multiple documents are updated at the same time atomically

C. Only one field in a document can be updated at a time

D. Documents are locked during any update operation

Solution

1. Step 1: Understand atomicity in MongoDB context

   MongoDB guarantees that updates to a single document are atomic, meaning all changes in that update happen fully or not at all.

2. Step 2: Compare options with this definition

   All changes to a single document happen completely or not at all correctly states this. Options A, B, and D describe behaviors that are not true for single document atomicity.

3. Final Answer:

   All changes to a single document happen completely or not at all -> Option A

4. Quick Check:

   Single document atomicity = All-or-nothing update [OK]

Hint: Atomic means all or nothing for one document update [OK]

Common Mistakes:

• Thinking atomicity applies to multiple documents
• Believing only one field updates atomically
• Assuming document locking happens automatically

2. Which of the following is the correct syntax to update a single document atomically in MongoDB?

easy

A. db.collection.update({ _id: 1 }, { name: 'Alice' })

B. db.collection.updateMany({ _id: 1 }, { $set: { name: 'Alice' } })

C. db.collection.modifyOne({ _id: 1 }, { $set: { name: 'Alice' } })

D. db.collection.updateOne({ _id: 1 }, { $set: { name: 'Alice' } })

Solution

1. Step 1: Identify the correct update method for one document

   The method updateOne updates a single document atomically. It uses a filter and an update operator like $set.

2. Step 2: Check each option's syntax

   db.collection.updateOne({ _id: 1 }, { $set: { name: 'Alice' } }) uses updateOne with $set, which is correct. db.collection.update({ _id: 1 }, { name: 'Alice' }) uses deprecated update without update operator. db.collection.modifyOne({ _id: 1 }, { $set: { name: 'Alice' } }) uses a non-existent method modifyOne. db.collection.updateMany({ _id: 1 }, { $set: { name: 'Alice' } }) updates many documents, not one.

3. Final Answer:

   db.collection.updateOne({ _id: 1 }, { $set: { name: 'Alice' } }) -> Option D

4. Quick Check:

   Use updateOne with $set for atomic single document update [OK]

Hint: Use updateOne with $set to update one document atomically [OK]

Common Mistakes:

• Using update without $set operator
• Using updateMany when only one document should update
• Using non-existent methods like modifyOne

3. Given the document { _id: 1, count: 5 }, what will be the document after this atomic update?

db.collection.updateOne({ _id: 1 }, { $inc: { count: 3 }, $set: { status: 'active' } })

medium

A. { _id: 1, count: 3, status: 'active' }

B. { _id: 1, count: 8, status: 'active' }

C. { _id: 1, count: 5 }

D. Update fails with error

Solution

1. Step 1: Understand the update operators used

   The $inc operator increases the count field by 3. The $set operator adds or updates the status field to 'active'.

2. Step 2: Calculate the new document values

   Original count is 5, incremented by 3 gives 8. The status field is set to 'active'.

3. Final Answer:

   { _id: 1, count: 8, status: 'active' } -> Option B

4. Quick Check:

   $inc adds 3, $set adds status [OK]

Hint: Combine $inc and $set to update fields atomically [OK]

Common Mistakes:

• Thinking $inc replaces the field instead of adding
• Ignoring $set operator effect
• Assuming update fails without errors

4. You wrote this update but it does not work as expected:

db.collection.updateOne({ _id: 2 }, { count: 10, status: 'done' })

What is the problem?

medium

A. The collection name is invalid

B. The filter {_id: 2} is incorrect syntax

C. Missing update operator like $set causes the update to replace the entire document

D. updateOne cannot update multiple fields at once

Solution

1. Step 1: Check the update document structure

   The update document must use update operators like $set to specify fields to change. Here, the update document lacks any operator.

2. Step 2: Understand MongoDB update syntax rules

   Without an operator, MongoDB treats the update document as a replacement document, overwriting the entire document. This causes unexpected behavior if other fields exist.

3. Final Answer:

   Missing update operator like $set causes the update to replace the entire document -> Option C

4. Quick Check:

   Always use $set or other operators in update document [OK]

Hint: Always use $set or operators in update documents [OK]

Common Mistakes:

• Forgetting $set causes full document replacement
• Assuming updateOne updates fields without operators
• Misunderstanding filter syntax

5. You want to update a user's profile atomically to change their email and increment their login count. Which update operation ensures atomicity and correctness?

db.users.updateOne(
  { _id: 123 },
  { $set: { email: '[e-mail]' }, $inc: { logins: 1 } }
)

Why is this update atomic and what would happen if you tried to update email and logins in two separate updateOne calls?

hard

A. This update is atomic because both changes happen together; separate calls risk partial updates

B. This update is not atomic; MongoDB cannot update two fields at once

C. Separate updateOne calls are better for performance and atomicity

D. Atomicity only applies to single field updates, so this is invalid

Solution

1. Step 1: Understand atomicity of single document updates

   MongoDB guarantees that all changes in a single updateOne call on one document happen fully or not at all, ensuring atomicity.

2. Step 2: Compare single update vs multiple updates

   Using one updateOne with both $set and $inc ensures both fields change together. Using two separate updateOne calls risks one succeeding and the other failing, causing inconsistent data.

3. Final Answer:

   This update is atomic because both changes happen together; separate calls risk partial updates -> Option A

4. Quick Check:

   Single updateOne call = atomic multi-field update [OK]

Hint: Combine changes in one updateOne call for atomicity [OK]

Common Mistakes:

• Thinking atomicity applies across multiple update calls
• Believing MongoDB can't update multiple fields atomically
• Assuming separate updates are safer