node.js - large number of databases in postgres - architectural best practices -


we using postgres in multi tenant nodejs set up. each client has separate database (and separate node process). connection pooling implemented each tenant using node-postgres module. because of increasing number of databases, hitting max_connections limit of postgres. increasing max_connections indefinitely not option (due connection overheads). should there change in architecture large number of databases? pointers appreciated.

the approach describe cannot scale: number of databases limiting factor.

you need redesign system. , correct approach depend entirely on project's requirements.

pointers designing system in general - that's broad subject. can start practical approach computer systems design , architecture, , thence research further, following project's requirements.


Comments

Popular posts from this blog

yii2 - Yii 2 Running a Cron in the basic template -

asp.net - 'System.Web.HttpContext' does not contain a definition for 'GetOwinContext' Mystery -

mercurial graft feature, can it copy? -