The issue is language ecosystems that don't use client side connection pooling because they're single threaded (node, Python). So scaling up the number of web server threads means scaling the number of Postgres processes, which are expensive.

This solves the latency but not the overhead--you'll end up with a full pool of connections for each running instance of your application.