@LiamKarlMitchell I'm not sure I see the advantage of using a child process to handle these requests. Can you explain your reasoning a bit more there. If that's the route I need to go, I'd rather find out now -- rather than later because of major issues arising. As it stands, using child process to handle the requests would have the added work of managing subprocesses in addition to multiple DB connections and that overhead just doesn't seem to have any immediate perks. Also, the aim the application is to have a single UI (application) installation that every user of the system would use; ie, everyone goes to myapp.com to interact with it -- but upon login, they would have a way to set a custom DB for their own data (data that doesn't drive the UI itself but functions of the application). Hope that makes sense.