Skip to content

Add duplicate causal consistency info #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 28, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 54 additions & 0 deletions dbx/causal-consistency.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
MongoDB enables **causal consistency** in client sessions.
The causal consistency model guarantees that operations within a session
run in a causal order. Clients observe results that are consistent
with the causal relationships, or the dependencies between
operations. For example, if you perform a series of operations where
one operation logically depends on the result of another, any subsequent
reads reflect the dependent relationship.

The following table describes the guarantees that causally
consistent sessions provide:

.. list-table::
:widths: 40 60
:header-rows: 1

* - Guarantee
- Description

* - Read your writes
- Read operations reflect the results of preceding write operations.

* - Monotonic reads
- Read operations do not return results that reflect an earlier data state than
a preceding read operation.

* - Monotonic writes
- If a write operation must precede other write operations, the driver
runs this write operation first.

For example, if you call |insert-one-method| to insert a document, then call
|update-one-method| to modify the inserted document, the driver runs the
insert operation first.

* - Writes follow reads
- If a write operation must follow other read operations, the driver runs
the read operations first.

For example, if you call |find-one-method| to retrieve a document, then call
|delete-one-method| to delete the retrieved document, the driver runs the find
operation first.

In a causally consistent session, MongoDB ensures a
causal relationship between the following operations:

- Read operations that have a |majority-rc| read concern
- Write operations that have a |majority-wc| write concern

.. tip::

To learn more about the concepts mentioned in this section, see the
following {+mdb-server+} manual entries:

- :manual:`Causal Consistency </core/read-isolation-consistency-recency/#causal-consistency>`
- :manual:`Causal Consistency and Read and Write Concerns </core/causal-consistency-read-write-concerns/>`