Single document atomicity in MongoDB - Step-by-Step Execution

Concept Flow - Single document atomicity

Start Transaction

↓

Modify Single Document

↓

Apply All Changes Atomically

↓

Commit Changes

↓

End Transaction

When you update a single document in MongoDB, all changes happen together or not at all, ensuring data stays consistent.

Execution Sample

MongoDB

db.users.updateOne(
  { _id: 1 },
  { $set: { name: "Alice", age: 30 } }
)

This updates the user with _id 1, changing name and age together in one atomic operation.

Execution Table

Step	Action	Document State Before	Change Applied	Document State After
1	Locate document with _id=1	{ _id: 1, name: "Bob", age: 25 }	None	{ _id: 1, name: "Bob", age: 25 }
2	Apply $set changes atomically	{ _id: 1, name: "Bob", age: 25 }	{ $set: { name: "Alice", age: 30 } }	{ _id: 1, name: "Alice", age: 30 }
3	Commit changes	{ _id: 1, name: "Alice", age: 30 }	None	{ _id: 1, name: "Alice", age: 30 }
4	End operation	{ _id: 1, name: "Alice", age: 30 }	None	{ _id: 1, name: "Alice", age: 30 }

💡 All changes applied atomically to the single document; operation completes successfully.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
document	{ _id: 1, name: "Bob", age: 25 }	{ _id: 1, name: "Bob", age: 25 }	{ _id: 1, name: "Alice", age: 30 }	{ _id: 1, name: "Alice", age: 30 }	{ _id: 1, name: "Alice", age: 30 }

Key Moments - 2 Insights

Why do both fields 'name' and 'age' change together and not separately?

Because MongoDB applies all updates to a single document atomically, as shown in execution_table step 2, so either all changes happen or none do.

What happens if the update fails halfway through?

The entire update is rolled back, so the document stays unchanged, ensuring atomicity as implied by the exit_note.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what changes are applied to the document?

A Only the 'name' field is changed

B Only the 'age' field is changed

C Both 'name' and 'age' fields are changed together

D No changes are applied

💡 Hint

Check the 'Change Applied' column at step 2 in execution_table

At which step does the document state first reflect the updated values?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Document State After' column in execution_table

If the update operation failed after applying changes but before commit, what would the final document state be?

A Original document unchanged

B Partially updated document

C Document deleted

D Document with only 'name' updated

💡 Hint

Refer to the atomicity principle explained in key_moments and exit_note

Concept Snapshot

Single document atomicity in MongoDB means all changes to one document happen together or not at all.
Use update operations like updateOne to modify fields.
If any part fails, no changes are saved.
This keeps data consistent and reliable.

Full Transcript

In MongoDB, when you update a single document, all changes are applied atomically. This means either all the changes happen together or none happen at all. For example, if you update the name and age fields of a user document, both fields change at the same time. The execution flow starts by locating the document, then applying all changes together, committing them, and ending the operation. If the update fails at any point, the document remains unchanged. This ensures data consistency and reliability.