Re: CouchDB 3.1.1 high disk utilization and degradation over time

2022-04-18 Thread Jan Lehnardt
Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/ *24/7 Observation for your CouchDB Instances: https://opservatory.app > On 4. Apr 2022, at 18:21, Roberto Iglesias wrote: > > Hello. > > About 1 year ago, we had two CouchDB 2.3.1 instances running inside

Re: CouchDB High Availablility deployment and ChangeFeed

2022-04-18 Thread Jan Lehnardt
Hi A, for your setup, we recommend using CouchDB Clustering to achieve high availability. But note that neither a single node nor a cluster _changes feed guarantees exactly-once-delivery. You have to solve that in your Spring-boot API. Best Jan — Professional Support for Apache CouchDB:

Re: Post/Comment DB design: Postgresql v/s CouchDB

2022-04-18 Thread Jan Lehnardt
Hi Meeka, we don’t generally recommend a per-user database system unless you deal with replication with e.g. PouchDB where each database needs distinct user access. For just a regular blog app, you can use a single database. The CouchDB docs explain just that example in fact. You’ll be working

Re: CouchDB 3.1.1 high disk utilization and degradation over time

2022-04-18 Thread Roberto Iglesias
Hi Jan, thanks for taking your time to read and answer my question. Did you account for the completely rewritten compaction daemon (smoosh) > that has a different configuration from the one in 2.x? Yes, I've taken this into account and adjusted my config to match what we expect. This is related