Question

first, here is what is said in Pymongo Documentation

By default, PyMongo starts a request for each thread when the thread first runs an operation on MongoDB. This guarantees **read-your-writes consistency. Within a request, the thread will continue to use the same socket exclusively, and no other thread will use this socket, until the thread calls end_request() or it terminates. At that point, the socket is returned to the connection pool for use by other threads.

so when using an async library to Mongodb (like Asyncmongo, Motor), will the user have a consistency like the one in blocking calls or an eventual consistency?

Answer 1

There are a couple of points about this question.

1. You aren’t guaranteed to have read-after-write consistency unless you’re using either "safe=true", "w=1" (or greater) or "j=true" with your write. You can either include these as part of the insert() or update() commands, or else use set_lasterror_options() to set these options for the connection, database, or collection that you’re using.

2. If you’re allowing reads from secondary nodes, (e.g. a ReadPreference other than PRIMARY), then you will not get read-after-write semantics, but only eventual consistency.

3. If you are using a ReadPreference of PRIMARY and you’re setting the appropriate lasterror options, then you’re guaranteed to get read-after-write semantics on all operations that use the same socket, that is, the same thread.

4. If you’re using multiple threads, and you are NOT reading from secondary nodes, then you’re guaranteed to get read-after-write consistency as long as you issue the read in the second thread after the write completes in the first thread. You can use standard thread synchronization primitives to assure this.