Bulk write operations in MongoDB - Step-by-Step Execution

Concept Flow - Bulk write operations

Prepare bulk operations array

↓

Start bulkWrite() call

↓

Execute each operation in order

↓

InsertOne

↓

Collect results

↓

Return summary of success/failures

Bulk write operations run many insert, update, or delete commands together in one call, improving speed and efficiency.

Execution Sample

MongoDB

db.collection.bulkWrite([
  { insertOne: { document: { name: "Alice" } } },
  { updateOne: { filter: { name: "Bob" }, update: { $set: { age: 30 } }, upsert: true } },
  { deleteOne: { filter: { name: "Charlie" } } }
])

This code runs three operations in bulk: insert Alice, update Bob's age or insert if missing, and delete Charlie.

Execution Table

Step	Operation Type	Details	Action Taken	Result
1	insertOne	Insert document { name: "Alice" }	Insert Alice document	InsertedCount: 1
2	updateOne	Filter: { name: "Bob" }, Update: { $set: { age: 30 } }, Upsert: true	Bob not found, insert new document	MatchedCount: 0, UpsertedCount: 1
3	deleteOne	Filter: { name: "Charlie" }	Charlie found and deleted	DeletedCount: 1
4	End	All operations processed	Bulk write completed	Summary returned

💡 All bulk operations executed in order; bulkWrite returns combined results.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
InsertedCount	0	1	1	1	1
MatchedCount	0	0	0	0	0
UpsertedCount	0	0	1	1	1
DeletedCount	0	0	0	1	1

Key Moments - 3 Insights

Why does updateOne with upsert:true insert a new document if no match is found?

Because upsert:true means 'update or insert'. If no document matches the filter, MongoDB inserts a new document with the update applied. See execution_table row 2.

Are bulk operations executed in parallel or in order?

Bulk operations run in the order they are listed, one after another. This ensures predictable results. See concept_flow and execution_table steps.

What happens if one operation in bulkWrite fails?

By default, bulkWrite stops at the first error unless ordered:false is set. This example assumes ordered:true, so it stops on error. See concept_flow and bulkWrite docs.

Visual Quiz - 3 Questions

Look at the execution_table, what is the InsertedCount after step 2?

A 1

B 0

C 2

D None

💡 Hint

Check the InsertedCount column in variable_tracker after After 2.

At which step does the bulkWrite perform a delete operation?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the Operation Type column in execution_table.

If upsert was false in step 2, what would happen?

A A new document would be inserted

B No document would be inserted or updated if Bob not found

C Charlie would be deleted twice

D Alice would be updated

💡 Hint

Refer to key_moments about upsert behavior and execution_table step 2.

Concept Snapshot

bulkWrite([{operation1}, {operation2}, ...]) runs many write ops in one call.
Operations include insertOne, updateOne, updateMany, deleteOne, deleteMany.
Runs in order; can stop on error or continue with ordered:false.
Returns summary counts: inserted, matched, upserted, deleted.
Use upsert:true to insert if no match on update.
Improves performance by reducing round trips.

Full Transcript

Bulk write operations in MongoDB let you run many insert, update, or delete commands together in one call. This example shows inserting a document named Alice, updating Bob's age or inserting if Bob doesn't exist, and deleting Charlie. Each operation runs in order. The updateOne with upsert:true inserts Bob if not found. The bulkWrite returns counts of inserted, matched, upserted, and deleted documents. This method is faster than running each operation separately because it reduces communication overhead with the database.