github-starred/couchdb-best-practices
2
0
Fork 0
mirror of https://github.com/jo/couchdb-best-practices.git synced 2026-05-16 06:06:00 -06:00
Code Issues 232 Projects Releases Packages Wiki Activity Actions

[GH-ISSUE #76] CouchDB 3 and the couch-per-use "plague" #986

New issue
Closed
opened 2026-04-27 22:01:13 -06:00 by gitea-mirror · 2 comments
gitea-mirror commented 2026-04-27 22:01:13 -06:00
Owner
Copy link

Originally created by @fredguth on GitHub (Apr 2, 2022).
Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/76

I have 2 questions:

  1. Has any of these best practices changed with CouchDB 3?
  2. What is your reaction on "Rule 5: Avoid the database-per-user anti-pattern like the plague" best practice from Cloudant?
Originally created by @fredguth on GitHub (Apr 2, 2022). Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/76 I have 2 questions: 1) Has any of these best practices changed with CouchDB 3? 2) What is your reaction on ["Rule 5: Avoid the database-per-user anti-pattern like the plague"](https://www.ibm.com/blogs/cloud-archive/2019/03/cloudant-best-and-worst-practices-part-1/) _best practice_ from Cloudant?
gitea-mirror commented 2026-04-27 22:01:16 -06:00
Author
Owner
Copy link

@jo commented on GitHub (Apr 3, 2022):

The best practices described here are also valid for CouchDB 3. However, I haven't worked with Linked Documents for a while, so this section may be outdated.

The DB-Per-User question is a bit complicated. It depends. The biggest bottleneg here is replication: the CouchDB replicator has its weaknesses when it comes to continuous intra-cluster replication. Here, the individual changes feeds are polled round-robin, which creates a high load. If validate doc update functions are also used, this load increases. Therefore, it may make sense to implement application-specific replication logic. That is, if the application knows when something changes, it can instruct single-shot replications, thus reducing the load.

I'm looking forward to the upcoming new features of CouchDB, especially the per-document access patterns, which would be a big step here.

<!-- gh-comment-id:1086856371 --> @jo commented on GitHub (Apr 3, 2022): The best practices described here are also valid for CouchDB 3. However, I haven't worked with Linked Documents for a while, so this section may be outdated. The DB-Per-User question is a bit complicated. It depends. The biggest bottleneg here is replication: the CouchDB replicator has its weaknesses when it comes to continuous intra-cluster replication. Here, the individual changes feeds are polled round-robin, which creates a high load. If validate doc update functions are also used, this load increases. Therefore, it may make sense to implement application-specific replication logic. That is, if the application knows when something changes, it can instruct single-shot replications, thus reducing the load. I'm looking forward to the upcoming new features of CouchDB, especially the per-document access patterns, which would be a big step here.
gitea-mirror commented 2026-04-27 22:01:17 -06:00
Author
Owner
Copy link

@fredguth commented on GitHub (Apr 4, 2022):

Thanks for the explanation!

<!-- gh-comment-id:1087353971 --> @fredguth commented on GitHub (Apr 4, 2022): Thanks for the explanation!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
gh-pages
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/couchdb-best-practices#986
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?