-
-
Notifications
You must be signed in to change notification settings - Fork 178
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-tenant #416
Comments
We have a concept of At the time I couldn't think a good usecase for namespace level filters. You could do what you suggested with a single tabel level |
Across databases its better to just have multiple instances of GraphJin |
Yeah I am interested in multi tenant with single db. It’s to save costs . A team with many services could use the one db and so save money and complexity. |
what if we support multiple roles for a single query that way member of org
x can be a role when applied it adds in its own filters along with the ones
for the other roles
|
I don’t understand how that helps a team ? Let’s say you have 10 orgs using a single db Each org has their own services. Say service A to D , so 4 services in their middle tier. I guess each on runs graphjin core . Each org shares roles , users and user to groups mapping . Typically an orgs services like to reuse their roles / users between their services. It’s a reasonably assumption. Each org would basically be isolated from the other orgs. That’s what I see as an archi type very often . mid org 1 outgrows the shared db, they migrate to their own db layer . |
I'm taking about the mechaism of achieving what you originally thought about "apply the org filter on all queries and mutations". We could achive this using the role mechanism even without adding |
yes you would have all that if we had multiple roles so a person A could have the roles "member_of_org_1, viewer, admin" and person B could have the roles ""member_of_org_2, viewer, user" |
Hey @dosco I got stuck on setup. I cant connect using cockroach. Hope you don't mind me trying it, even though not officially supported. heres the issue:
REPRO: makefile:
|
Still trying to work it out :) This golang web admin can connect with that $(DB_URL).
|
I can imagine that sone people may want to use the filter concepts to do multi tenant also.
So an org has certain roles and users. When an org connects we detect the org via sone header ( or otherwise ) and then apply the org filtere on all queries and mutations . It’s a middleware guard that is always applied.
the roles and users are available to that org user over the introspection api too based on org , so that any IDE is multi tenant aware.
I don’t know if the filters conceit would be enough to restrict table access.
The text was updated successfully, but these errors were encountered: