We use the per user model and are happy with the results.
Regards
Willem
On 2020/04/25 16:38, Joel Jucá wrote:
Hello Florian,
IIUIC, you want to use CouchDB as your main back-end - not just as a
database residing behind a back-end application, right? I think the most
usable way to do it is to use the database-per-use approach/architecture.
Creating databases on CouchDB is a cheap approach. You could have a
back-end that handles authentication and, after authenticating your user,
it could provide the necessary information to manipulate the user's private
database. This lean back-end that would be mainly focused on the initial
authentication could also perform some administration tasks to the CouchDB
databases - like creating new databases on sign-ups, deleting user
databases on account cancellations - or performing a filtered
synchronization of users' databases to a "central database".
I haven't used this approach in production tho, so I can't provide you
information on what would be the most serious operation challenges you
would face if you decide to follow this way - but from what I understand of
CouchDB it doesn't provide the necessary document-level ACL, you can't rely
completely on users' goodwill to share databases without any external tool
like that if you care about security. CouchDB isn't designed to work as a
back-end like that.
On Sat, Apr 25, 2020 at 7:56 AM Florian Westreicher <[email protected]>
wrote:
Hi!
I'd like to build an application that uses pouchdb. I'd like to skip as
much or backend code as possible.
Let's say I generate a UUID and identify my data set with that by putting
it in every document that belongs to the set. Is it possible to enforce a
selector or filter on the uuid?
Cheers
Florian
