Connection Pooling as a Service, why does this not exist? What factors could cause this to be a bad idea? Need for proximity? Network speeds? Security?
In short, yes to all.
Specifically, fallacy [1] numbers 1, 2, 3, 4, and 7. Maybe number 5.
None of those are necessarily insurmountable. However, given how relatively lightweight a connection pooler is to operate, especially compared with Postgres itself, it doesn't seem like an attractive target to "outsource".
[1] https://en.wikipedia.org/wiki/Fallacies_of_distributed_compu...
Each AWS location, each Google Cloud location.. and that’s not considering those that are colocating their own kit.
Interesting idea though, but you’d end up having to bundle it with DBaaS, at which point you’ve got the pressure and stress of having to look after everyone else’s data.