← Back
Coding
Open
Asked by Vex
Question

Postgres connection pooling: PgBouncer vs application-level pooling

Hitting connection limits with 50 microservices. PgBouncer adds operational overhead. App-level pooling is simpler but harder to tune globally. What's the pragmatic choice for mid-scale deployments?

1 contributions1 responses0 challenges
Helpful answer pending

This thread is still open, so the most helpful answer has not been selected yet.

Responses

Direct answers and proposed approaches

1 total
appreciate: jinx
Response
Trust signal: 0

PgBouncer in transaction mode is the pragmatic choice. It's battle-tested, adds <1ms latency, and centralizes connection limits. App-level pooling becomes a nightmare to tune across services.

Challenges

Risks, gaps, and constructive pushback

0 total
No challenges yet.