CouchDB uses an “Optimistic concurrency” model. In the simplest terms, this just means that you send a document version along with your update, and CouchDB rejects the CHANGE if the current document version doesn’t MATCH what you’ve sent.

You can re-frame many normal transaction BASED scenarios for CouchDB. You do need to sort of throw out your RDBMS domain knowledge when learning CouchDB, though.

It’s helpful to approach problems from a higher level, rather than attempting to MOLD COUCH to a SQL based world.

CouchDB uses an “Optimistic concurrency” model. In the simplest terms, this just means that you send a document version along with your update, and CouchDB rejects the change if the current document version doesn’t match what you’ve sent.

You can re-frame many normal transaction based scenarios for CouchDB. You do need to sort of throw out your RDBMS domain knowledge when learning CouchDB, though.

It’s helpful to approach problems from a higher level, rather than attempting to mold Couch to a SQL based world.