These are chat archives for Automattic/mongoose
@tylerdmace To me it sounds like you may be better off firing up child processes to manage requests from each user depending on the db they need rather than managing a connection pool per db?
If you are writing software as a service then that could be way to go?
Although others may argue you should have a different server/virtual machine/deployment altogether.
Having child processes may separate your concerns of (What happens if program X crashes everyone else can't use it?, and could also mitigate worries about any sensitive information leaking out to another user)
But I digress