What is Connection Pool?

What is a Connection Pool?

A connection pool lets an application reuse existing database connections instead of opening a fresh connection for every request. Creating a connection requires authentication, network handshakes, and server-side resources, so the overhead becomes expensive under traffic.

How Does It Work?

When the application starts, or when the first request arrives, a number of connections are opened and kept in the pool. A request borrows an available connection, runs its query, and returns the connection to the pool instead of closing it. If the pool is full, new requests may wait, fail fast, or create more connections up to a configured limit.

With databases such as PostgreSQL, pool settings must be planned together with the number of application instances. If every replica opens its own pool, the total connection count can exceed the database limit quickly.

Key Settings

• Minimum and maximum connections: Balance idle resource usage against traffic spikes.
• Idle timeout: Decides when unused connections are closed.
• Acquire timeout: Limits how long a request waits for a connection.
• Health checks: Prevent broken connections from being reused.

Business Use

Connection pools help reporting dashboards, e-commerce carts, and multi-user SaaS applications run SQL queries with more predictable latency. A poorly sized pool can still overload the database, so real traffic, query duration, and worker counts need to be measured together.