Instead of creating a new connection with every request, connection poolers reuse some existing connections. ... It prevents the overhead of creating a new connection to the database

every time there is a request for a database connection with the same properties (i.e name, database, protocol version).

Why do we use connection pooling?

Using connection pools helps to both alleviate connection management overhead and decrease development tasks for data access. Each time an application attempts to access a backend store (such as a database), it requires resources to create, maintain, and release a connection to that datastore.

Why does using a database connection Pooler improve the security posture of an application?

Connection pooling is a technique used to avoid the overhead of making a new database connection every time an application or server object requires access to a database. ... A database connection pool avoids this bottleneck. The overhead time for establishing a database connection is typically around 1 to 3 seconds.