Transactions vs atomic document writes in MongoDB

Introduction

Transactions and atomic document writes help keep your data safe and correct when many changes happen at once.

When you need to update multiple documents and want all changes to succeed or fail together.

When you update only one document and want to make sure the change is complete and safe.

When you want to avoid partial updates that can cause wrong or broken data.

When you want to keep your data consistent even if something goes wrong during updates.

Syntax

MongoDB

/* Atomic document write example */
db.collection.updateOne({ _id: 1 }, { $set: { field: 'value' } })

/* Transaction example */
const session = client.startSession();
await session.withTransaction(async () => {
  await db.collection1.updateOne({ _id: 1 }, { $set: { field: 'value1' } }, { session });
  await db.collection2.updateOne({ _id: 2 }, { $set: { field: 'value2' } }, { session });
});

Atomic document writes affect only one document and are always all-or-nothing.

Transactions can include multiple operations on many documents or collections and commit all changes together.

Examples

This updates the name field in one user document atomically.

MongoDB

db.users.updateOne({ _id: 123 }, { $set: { name: 'Alice' } })

This transaction updates an order and inventory together. Both changes succeed or both fail.

MongoDB

const session = client.startSession();
await session.withTransaction(async () => {
  await db.orders.updateOne({ _id: 1 }, { $set: { status: 'shipped' } }, { session });
  await db.inventory.updateOne({ _id: 10 }, { $inc: { stock: -1 } }, { session });
});

Sample Program

This example transfers 100 units from account A to account B using a transaction to keep data safe.

MongoDB

const session = client.startSession();
try {
  session.startTransaction();
  await db.accounts.updateOne({ _id: 'A' }, { $inc: { balance: -100 } }, { session });
  await db.accounts.updateOne({ _id: 'B' }, { $inc: { balance: 100 } }, { session });
  await session.commitTransaction();
  console.log('Transaction committed');
} catch (error) {
  await session.abortTransaction();
  console.log('Transaction aborted');
} finally {
  session.endSession();
}

Important Notes

Atomic writes are simpler and faster but only work on single documents.

Transactions are more powerful but can be slower and need more setup.

Use transactions when you must update multiple documents together to keep data correct.

Summary

Atomic document writes update one document completely or not at all.

Transactions group many operations so they all succeed or fail together.

Choose atomic writes for simple single-document changes and transactions for complex multi-document updates.

Practice

1. Which statement best describes atomic document writes in MongoDB?

easy

A. They require manual rollback on failure.

B. They group multiple documents to update together.

C. They allow partial updates on multiple documents.

D. They update a single document completely or not at all.

Solution

1. Step 1: Understand atomic writes scope

   Atomic writes in MongoDB apply only to single documents, ensuring full update or no update.

2. Step 2: Compare with multi-document operations

   Multi-document updates require transactions, not atomic writes.

3. Final Answer:

   They update a single document completely or not at all. -> Option D

4. Quick Check:

   Atomic writes = single document update [OK]

Hint: Atomic writes affect one document fully or not at all [OK]

Common Mistakes:

• Thinking atomic writes cover multiple documents
• Confusing atomic writes with transactions
• Assuming partial updates are atomic

2. Which of the following is the correct way to start a transaction in MongoDB using the shell?

easy

A. session.startTransaction()

B. db.startTransaction()

C. transaction.begin()

D. start.transaction()

Solution

1. Step 1: Recall MongoDB transaction syntax

   Transactions start on a session object using startTransaction() method.

2. Step 2: Verify options

   Only session.startTransaction() matches the correct syntax.

3. Final Answer:

   session.startTransaction() -> Option A

4. Quick Check:

   Start transaction = session.startTransaction() [OK]

Hint: Use session.startTransaction() to begin transactions [OK]

Common Mistakes:

• Using db.startTransaction() which is invalid
• Confusing method names like transaction.begin()
• Incorrect method call syntax

3. Given the following code snippet, what will be the result if one update fails inside the transaction?

const session = client.startSession();
session.startTransaction();
try {
  await collection.updateOne({ _id: 1 }, { $set: { value: 10 } }, { session });
  await collection.updateOne({ _id: 2 }, { $set: { value: 20 } }, { session });
  await session.commitTransaction();
} catch (e) {
  await session.abortTransaction();
}

medium

A. Both updates are applied or none if any fails.

B. Only the first update is applied if the second fails.

C. Both updates are applied regardless of errors.

D. Updates are applied partially without rollback.

Solution

1. Step 1: Understand transaction behavior

   Transactions ensure all operations succeed or all fail together.

2. Step 2: Analyze code flow

   If any update fails, catch block aborts transaction, rolling back changes.

3. Final Answer:

   Both updates are applied or none if any fails. -> Option A

4. Quick Check:

   Transaction = all or nothing [OK]

Hint: Transactions commit all or rollback all changes [OK]

Common Mistakes:

• Assuming partial updates apply on failure
• Ignoring abortTransaction() effect
• Thinking updates apply independently

4. Identify the error in this MongoDB transaction code snippet:

const session = client.startSession();
session.startTransaction();
await collection.updateOne({ _id: 1 }, { $set: { value: 10 } });
await session.commitTransaction();
session.endSession();

medium

A. updateOne cannot be used inside transactions.

B. Missing session option in updateOne call.

C. startTransaction() must be called after updateOne.

D. session.endSession() should be called before commitTransaction().

Solution

1. Step 1: Check transaction usage in updateOne

   Operations inside a transaction must include the session option to link them.

2. Step 2: Verify code calls

   updateOne lacks { session } option, so it runs outside transaction.

3. Final Answer:

   Missing session option in updateOne call. -> Option B

4. Quick Check:

   Include session in operations inside transactions [OK]

Hint: Always pass { session } to operations inside transactions [OK]

Common Mistakes:

• Forgetting to pass session option in operations
• Calling endSession before commitTransaction
• Misordering startTransaction call

5. You need to update a user's profile document and also add a log entry in a separate collection. Which approach is best to ensure both updates succeed or fail together?

hard

A. Perform two separate atomic document writes without transactions.

B. Update the profile document atomically and ignore the log entry.

C. Use a transaction to update both collections atomically.

D. Update the log entry first, then the profile document without transactions.

Solution

1. Step 1: Identify multi-document update requirement

   Updating two collections means multiple documents involved.

2. Step 2: Choose appropriate method

   Transactions ensure both updates succeed or fail together, preserving consistency.

3. Final Answer:

   Use a transaction to update both collections atomically. -> Option C

4. Quick Check:

   Multi-document update = use transactions [OK]

Hint: Use transactions for multi-document atomic updates [OK]

Common Mistakes:

• Using atomic writes for multiple collections
• Ignoring failure possibility in one update
• Assuming separate writes are automatically atomic