Feature 17 Multitenancy support in sql-dao library#18
Conversation
55d6f48
into
eclipse-ecsp:17-feat-abstractroutingdatasource-implementation-for-multitenancy
1 check passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please refer to our contributing docs for any questions on submitting a pull request.
Issues are required for both bug fixes and features.
Resolves #17
Describe behaviour before the change
Before this change, only single tenant support was there in the sql-dao library.
Describe behaviour after the change
SQL DAO library now has the support for multiple tenants in a single deployment. Services can configure the tenantIds, enable the multi-tenant feature and SQL DAO library will be able to construct and connect to tenant specific datasources and using Spring's AbstractRoutingDataSource, it will also be able to route each request to tenant specific datasource.
Pull request checklist
Does this introduce a breaking change?