Database Connection Pooling

When to use

• The user sees per-request overhead from opening a fresh DB connection (TCP handshake, TLS, auth) and wants to reuse connections to cut latency.
• The user hits "Too many connections" errors, or the database is saturated by more client connections than it can serve, and needs to bound and pool them.
• The user is deciding how to reuse connections given their runtime — PHP-FPM, Swoole/RoadRunner workers, or serverless — and wants the right strategy.

When NOT to use