Write Concern in MongoDB: What It Is and How It Works

In MongoDB, write concern is a setting that controls the level of acknowledgment requested from the database when writing data. It determines how many nodes must confirm the write before it is considered successful, helping ensure data durability and consistency.

How It Works

Think of write concern as a way to ask MongoDB, "How sure do you want me to be that my data is saved?" When you write data, MongoDB can confirm the write in different ways. For example, it can tell you immediately that it received the write request, or it can wait until the data is saved on multiple servers.

This is like sending a letter and asking for a receipt. You can choose to get a receipt from just one post office or from several offices along the way. The more receipts you ask for, the more confident you are that your letter arrived safely, but it might take longer.

In MongoDB, you set the write concern level using options like w: 1 (acknowledge from primary server), w: majority (acknowledge from most servers), or w: 0 (no acknowledgment). This controls how MongoDB confirms the write operation.

Example

This example shows how to set write concern in a MongoDB insert operation using the MongoDB shell. It requests acknowledgment from the majority of replica set members before confirming the write.

javascript

db.collection.insertOne(
  { name: "Alice", age: 30 },
  { writeConcern: { w: "majority", wtimeout: 5000 } }
)

Output

{ "acknowledged" : true, "insertedId" : ObjectId("...") }

When to Use

Use write concern to balance between speed and data safety. If you want fast writes and can tolerate some risk of data loss, use a lower write concern like w: 1. For critical data where losing writes is unacceptable, use w: majority to ensure data is saved on most servers.

For example, financial transactions or user account updates should use higher write concern to avoid data loss. On the other hand, logging or analytics data might use lower write concern to improve performance.

Key Points

• Write concern controls how MongoDB confirms write operations.
• Higher write concern means more data safety but slower writes.
• Common values are w: 0, w: 1, and w: majority.
• Use appropriate write concern based on your application's needs.

Key Takeaways

Write concern sets how many servers must confirm a write before success.

Higher write concern improves data safety but can slow down writes.

Use 'majority' write concern for critical data to ensure durability.

Lower write concern can be used for faster writes when some risk is acceptable.

Always choose write concern based on your application's reliability needs.