The downside of a map of pools is that it is not as dynamic as a design
that just "prefers" affinity with an arbitrary key. The map of pools works
well when you are connection rich and tenant poor, however when you have a
scenario where you may be facing 2x tenants to db connections with
sparse usa
Hi jessie,
Think it can makes sense but not sure it fits in commons-dbcp "core" since
the best is generally to not merge the connection in the same pool but use
N pools and enable the database to inject a custom "router"/selector
(that's what spring or tomee did for ex [1]/[2]).
The rational to do
Hi Jesse,
Please take a look at Commons DBCP and how your proposal would fit in.
Gary
On Wed, Nov 8, 2023, 4:49 PM Jesse Harris
wrote:
> Would there be any interest in contributing an implementation of a multi
> tenant connection pool implementation?
>
> One implementation of a multi-tenant ar
