mirror of
https://github.com/jo/couchdb-best-practices.git
synced 2026-05-15 14:16:00 -06:00
[GH-ISSUE #73] One database per user versus Crypto Pouch #781
Labels
No labels
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/couchdb-best-practices#781
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @fredguth on GitHub (Jan 6, 2019).
Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/73
I am used to the "one database per user" pattern, but I say that one can prevent using one database per user and accomplish per document access permission with crypto pouch. How would that be? Could you elaborate?
@jo commented on GitHub (Apr 3, 2022):
Yes, this is indeed a possibility. One thing to keep in mind, though: replication performance is a little slow when using filters. So having one giant database for all users would require each user to do filtered replication.
@fredguth commented on GitHub (Apr 4, 2022):
Several applications in the SaaS business model may have one-db-per-tenant with several users (team members) sharing the same db and controlling access via crypto pouch. I guess this could avoid filtered replication, but I guess the possible down sides of #76 can still happen. I am wondering about custom replication, as you suggested. Is there documentation on this kind of replication?