Isn’t it supposed to be mainly REST based and have a goal of being able to sync multiple nodes with expected connection loss in between?
I’ve never needed that on a project but it seems like it would work for some use cases. I hear good things about PouchDB.
Couch has always been good at this use case where systems on both ends may have changed in the disconnect time.
We use transactions under the hood actually writing data to indexeddb
I fully admit I'm not very well-versed on databases or distributed computing, happy to have things clarified.
1. Additional (p2p) use cases, honestly I dont use CouchDB much these days, I use express-pouchdb-server so I can embed pouchdb into my server easier than any other database, there is also pouchdb-server and p2p projects like Thali (http://thaliproject.org/)
2. CouchDB existed, sync is super hard, writing an edge client would have meant designing it myself, writing a couchdb clone meant I needed to make a lot less decisions about how it worked while being very confident it would work, The test suite runs the same tests against pouchdb/couchdb to ensure compatibility (and replication via each configuration)
I can understand it working the other way around, e.g. an application initially seems good, but opinion of it drops when finding out it's written in COBOL.
I can understand if the CouchDB authors agreed with criticism of their application, and explained them as being inherent to the language. AFAIK they haven't. EDIT: Ah, looks like the author wrote CouchDB!
I can understand if Erlang and its proponents held CouchDB up as a shining example of their philosophy. AFAIK they don't (e.g. it doesn't appear on https://www.erlang.org/community ).