I am not an expert regarding CouchDB so cannot answer your question
directly.
You might find the CouchDB Definitive Guide page on Eventual Consistency
interesting <http://guide.couchdb.org/draft/consistency.html>. You
should think carefully about your requirements for consistency.
On 28/12/2016 10:09, Kaveh Shahbazian wrote:
Is there a way to do multi-doc transaction in CouchDB? Single Node? Cluster?
CouchDB as a document database has some nice characteristics for developing
an e-commerce system. For example a product can just get embedded inside
the order! This way we have a snapshot of the product at that specific
time. It needs lots of housekeeping in a RDBMS. Or dealing with instances
of a product (instances of a SKU) is much nicer in the same way (if you are
going to have an inventory too); which in turn provide interesting
information in the long run for data analysis.
But sometimes we just need a transaction.
I've read some papers & blogs here & there and wondered if it is more
feasible to do a total rewrite and use (say) PostgreSQL for my (rather
small) website/app.
But if there is already a simple to use utility for transactions in
CouchDB, I could still enjoy the things CouchDB gives me and use the
transaction part just when needed.
Best;
