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 through Database per Client #749

Open
jeremydmiller opened this Issue May 6, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@jeremydmiller
Contributor

jeremydmiller commented May 6, 2017

I wanted to split up #435.

The idea here would be to keep each tenant in a completely separate database. We've already made some significant changes for 2.0 to make this a lot more efficient inside of Marten's internals. Here's what I think still needs to happen:

  • A tenanting strategy that can lookup the database connection string per tenant
  • At development time (AutoCreate != AutoCreate.None), be able to spin up a new database on the fly for a tenant
  • "Know" what all the existing tenants are
  • Be able to apply all document schema operations on all tenants
  • Might be an extension to the command line project to apply changes to all tenant databases at a time
@jeremydmiller

This comment has been minimized.

Show comment
Hide comment
@jeremydmiller

jeremydmiller Jun 8, 2017

Contributor

I'm dropping this off of the 2.0 release. When we do this, we'll need to change quite a few things in QueryHandlerFactory and the async daemon to not depend on the store's default tenant.

Contributor

jeremydmiller commented Jun 8, 2017

I'm dropping this off of the 2.0 release. When we do this, we'll need to change quite a few things in QueryHandlerFactory and the async daemon to not depend on the store's default tenant.

@jeremydmiller jeremydmiller modified the milestones: 2.1, 2.0 Jun 8, 2017

@jeremydmiller jeremydmiller modified the milestone: 2.1 Aug 11, 2017

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