Please submit this form to view the presentation.

ReadConcern and WriteConcern

ReadConcern and WriteConcern

August 11, 2017

Facebook ShareLinkedin ShareReddit ShareTwitter ShareGoogle+ Share

MongoDB replica sets allow you to make the database highly available so that you can keep your applications running even when some of the database nodes are down. In a distributed system, local durability of writes with journaling is no longer enough to guarantee system-wide durability, as the node might go down just before any other node replicates new write operations from it. As such, we need a new concept of cluster-wide durability.

How do you make sure that your write operations are durable within a replica set? How do you make sure that your read operations do not see those writes that are not yet durable? This talk will cover the mechanics of ensuring durability of writes via write concern and how to prevent reading of stale data in MongoDB using read concern. We will discuss the decision flow for selecting an appropriate level of write concern, as well as associated tradeoffs and several practical use cases and examples.

*Learning Objectives: *

  • Introduction to the concepts of write concern and read concern.
  • How to make a decision on what priority levels to set and associated tradeoffs to consider.
  • Practical use cases for applying write and read concerns.

Try MongoDB Atlas, our fully-managed
database as a service.

Available on AWS, Azure, and GCP.