-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Feature Request: spring-boot-multitenancy-starter #28812
Comments
Thanks for the suggestion, but I don't think that multi-tenancy is something that Spring Boot can have a strong enough opinion about to warrant having an auto-configuration and a starter for it. For example, there's no guarantee that a multi-tenant application will be using a DataSource or that it will be using OAuth. I think there are just too many variables around each individual application's approach to multi-tenancy for Boot to do anything meaningful. Thanks again for the suggestion though. |
@wilkinsona Perhaps narrowing it down to a cool abstraction for datasource proxying in spring-data (jpa/mongo etc..) would be more resonable and maybe not callign it spring-boot-multitenancy but spring-boot-data-multitenancy? |
If you haven't already seen them, you may want to look at Spring Framework's I still don't see any scope for Spring Boot auto-configuring anything at this point. We'd like to offer support for auto-configuring multiple |
Amazing thanks! |
I think this is the starter I miss the most in this near perfect framework. It should be an autconfiguration for multitenant setups, which nicely integrates with spring-data (for datasource resolution), spring-oauth2-resource-server (since tenantId could come from a token jwt claim), and spring-logging (for contextualization of tenant as an MDC property). I guess a custom centralized service would still be needed to store all tenant informations, but it still would speed up a lot this typical need
Just a proposal :)
The text was updated successfully, but these errors were encountered: