To my understanding each read pulls from the last good MVCC checkpoint/revision/what-have-you so there are no read locks due to writes. Nor do any reads lock other reads. Then each write on a single file are done serially so there are no write locks.
I believe each database and each view are in their own separate file so they can all be written to concurrently. Not positive on that though. On Thu, Aug 18, 2011 at 1:49 PM, Danny Sinang <[email protected]> wrote: > Hello, > > CouchDB claims to be lockless, thanks to its use of MVCC. Both CouchDB and > MarkLogic claim to use MVCC. > > However, http://www.odbms.org/download/inside-marklogic-server.pdf states > that MarkLogic does read and write locking for updates. > > Does CouchDB also do the same ? If not, how does it do updates differently > ? > > Regards, > Danny > -- “The limits of language are the limits of one's world. “ -Ludwig von Wittgenstein
