You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to understand more on the abstractRouting that spring offers.
Wouldn’t a hashmap suffice the purpose of the lookup. I am trying to understand what advantage does the thread bound context brings in abstract routing ?
What advantages does the AbstractRoutingDatasource brings in specific, since the same could be achieved using a simple if-else logic to determine the target from the hashmap?
The text was updated successfully, but these errors were encountered:
Surely it is not the only way to achieve multitenancy in an application, it's just that it is nicely integrated to Spring Boot and requires minimal plumbing to integrate it.
What would your implementation with HashMap look like?
I don't know what's being asked exactely. I am sure there are alternative approaches. But the AbstractRoutingDataSource is probably the easiest way when using the Spring Framework and it integrates well into it.
I am trying to understand more on the abstractRouting that spring offers.
The text was updated successfully, but these errors were encountered: