3 ms·

Care to elaborate on "couchdb has fallen out of favour"? Currently evaluating it for the very case you describe

by rom99 5y ago

uniqueuid 5y ago
Well, I've read about couchdb every few years, and people in the last ~5 years were complaining about an awkward query syntax, slow embedded JS engine (IIRC), client-side complexity of the document data model and effort to maintain. Similar things could probably be said about mongodb. If your data is small enough, it probably doesn't matter.
- rom99 5y ago
  Thanks, we're not dealing with very large data sizes: maybe up to 100K documents, maybe using large binary attachments up to 100s MB per attachment. We use another DB product (ArangoDB) as our main application DB, so would be using something like CouchDB only for the offline-first and peer-to-peer replication capability - then referencing items in CouchDB from our main application DB, where we're more than happy about query language and other features. I had a somewhat wild idea that someone (maybe us...) could implement the couch DB replication protocol for ArangoDB using the ArangoDB FOXX framework. Not sure how feasible that might turn out to be though, wonder if anyone else thought of it...
couchaway9000 5y ago
I started using CouchDB around 2010. Overtime CouchDB has been removing more and more functionality and features that made CouchDB great IMHO (e.g couchapps), the 2.x (IIRC) made a lot of changes and totally broke a large application and made it too challenging to update so we stayed on a 1.x version (whatever version was last before the big couch merge.) we're moving off of Couch entirely in the future. I'd have a look at Couchbase if you're looking for replication features too.
ies7 5y ago
We have a pwa with pouchdb sync thousands handphones from couchdb every morning. Couchdb sync is great and pouchdb take care the db of whatever browser in your user phone. I could say we pick couchdb just because of their sync and pouchdb. For our main db we use postgres.

Care to elaborate on "couchdb has fallen out of favour"? Currently evaluating it for the very case you describe

by rom99 5y ago

Care to elaborate on "couchdb has fallen out of favour"? Currently evaluating it for the very case you describe

Well, I've read about couchdb every few years, and people in the last ~5 years were complaining about an awkward query syntax, slow embedded JS engine (IIRC), client-side complexity of the document data model and effort to maintain. Similar things could probably be said about mongodb. If your data is small enough, it probably doesn't matter.

rom99 5y ago
Thanks, we're not dealing with very large data sizes: maybe up to 100K documents, maybe using large binary attachments up to 100s MB per attachment. We use another DB product (ArangoDB) as our main application DB, so would be using something like CouchDB only for the offline-first and peer-to-peer replication capability - then referencing items in CouchDB from our main application DB, where we're more than happy about query language and other features. I had a somewhat wild idea that someone (maybe us...) could implement the couch DB replication protocol for ArangoDB using the ArangoDB FOXX framework. Not sure how feasible that might turn out to be though, wonder if anyone else thought of it...

couchaway9000 5y ago

I started using CouchDB around 2010. Overtime CouchDB has been removing more and more functionality and features that made CouchDB great IMHO (e.g couchapps), the 2.x (IIRC) made a lot of changes and totally broke a large application and made it too challenging to update so we stayed on a 1.x version (whatever version was last before the big couch merge.) we're moving off of Couch entirely in the future. I'd have a look at Couchbase if you're looking for replication features too.

ies7 5y ago

We have a pwa with pouchdb sync thousands handphones from couchdb every morning. Couchdb sync is great and pouchdb take care the db of whatever browser in your user phone. I could say we pick couchdb just because of their sync and pouchdb. For our main db we use postgres.