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 via Schema per Tenant #752

Open
jeremydmiller opened this Issue May 6, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@jeremydmiller
Contributor

jeremydmiller commented May 6, 2017

Originally part of #435, but busting it out now.

Before we tackle this one, we need to decide if we want to retain the ability to put different document types on different schemas.

Strangely enough, I think this is the hardest of the 3 types of multi-tenancy because of Marten internals.

@ejsmith

This comment has been minimized.

Show comment
Hide comment
@ejsmith

ejsmith Jul 26, 2017

Contributor

Trying to figure out what benefit this would provide over just using a IDocumentStore factory in the app. This seems like a pretty obscure feature that would add complexity. I'm guessing this is something that your team is wanting internally?

Contributor

ejsmith commented Jul 26, 2017

Trying to figure out what benefit this would provide over just using a IDocumentStore factory in the app. This seems like a pretty obscure feature that would add complexity. I'm guessing this is something that your team is wanting internally?

@jeremydmiller

This comment has been minimized.

Show comment
Hide comment
@jeremydmiller

jeremydmiller Jul 26, 2017

Contributor

I don't think this one's getting done any time soon, or at least not until we ditch the idea that different documents are in a different schema. The DocumentStore object is expensive, and you'd have to recreate and compile on the fly a lot of objects and expressions for each tenant, hence this story and the related one for a database per tenant

Contributor

jeremydmiller commented Jul 26, 2017

I don't think this one's getting done any time soon, or at least not until we ditch the idea that different documents are in a different schema. The DocumentStore object is expensive, and you'd have to recreate and compile on the fly a lot of objects and expressions for each tenant, hence this story and the related one for a database per tenant

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