Postgres has been my DB of choice for nearly a decade. The 
only times I wind up working with another db are because:<p>(1 it is a better technical fit for a very specific problem<p>(2 there is already a legacy db in place<p>I have been voted down at a couple of startups that wanted to run a &quot;MEAN&quot; stack, invariably all of those startups moved from MongoDB or shutdown.<p>The only time I will advocate for anything other than Postgres is when Wordpress is involved. If the data model is simple enough then MySQL is more than up for the task, and it avoids an additional database dependency.<p>Thankfully all the ORM&#x27;s that are worth using support MySQL and Postgres, so using both is very doable.<p>### Useful Postgres (or SQL in general) tools&#x2F;libraries :<p>Bookshelf ORM <a href="http:&#x2F;&#x2F;bookshelfjs.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;bookshelfjs.org&#x2F;</a><p>PostgREST automated REST API <a href="https:&#x2F;&#x2F;github.com&#x2F;begriffs&#x2F;postgrest" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;begriffs&#x2F;postgrest</a><p>Sqitch git style migration management <a href="http:&#x2F;&#x2F;sqitch.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;sqitch.org&#x2F;</a>