Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-tenancy support #1539

Open
wohali opened this issue Aug 7, 2018 · 4 comments
Open

Multi-tenancy support #1539

wohali opened this issue Aug 7, 2018 · 4 comments

Comments

@wohali
Copy link
Member

wohali commented Aug 7, 2018

Cloudant has this. Would be great if open source CouchDB had this too.

Depends on #1504 .

@janl
Copy link
Member

janl commented Aug 8, 2018

I have a node.js based proxy prototype of this (closed source at the moment) that could help with inspiration. I might be able to share its test suite in the future.

@manobi
Copy link

manobi commented Nov 14, 2018

I have used Couchdb in past as a secondary database in SaaS apps it was never my main storage.
I'm not sure if I really need multi-tenancy builtin, because it would increase the docs complexity.

But I would love to see the proxy @janl mentioned, actually I'm planing to port an tenant handler we have from PHP to node.js and open source it (it's actually for mysql but I can create wrapper for other database).

Can you share something about the common strategies used? one database per tenant or all data in a single database and proxy controls what each tenant can see?

@wohali
Copy link
Member Author

wohali commented Nov 14, 2018

@manobi you may also want to look at the _access proposal for CouchDB 3.0, which helps with the latter scenario. I think this might be better for your situation, frankly. See #1524 for details.

@manobi
Copy link

manobi commented Nov 15, 2018

@wohali Thanks for sharing, I will be following your recommendation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants