Automatically scale pool maximum connections about database-kit HOT 1 OPEN

One issue I can see with querying the number of connections available/used is that it might cause problems if your app scales horizontally. E.g. if you have 300 connections and one app instance, we might choose

max_connections - some_buffer / number of workers

So let's say 200. However, if we then scale up to 5 instances we either end up in the situation where each app is trying to use 200 connections (so 1000 attempted connections for 300 max connections) or one instance has 200 and the other 4 have to share the remaining 100, meaning that they're less performant

from database-kit.