Connection Pool - Applications

Applications

Connection pooling being normally used in web-based and enterprise applications is usually handled by an application server. Any dynamic web page can be coded to open a connection and close it normally but behind the scenes when a new connection is requested, one is returned from the connection pool maintained by the application server. Similarly, when a connection is closed it is actually returned to the connection pool.

Connection pooling is not limited to using application servers. Traditional applications that need frequent access to databases can benefit from connection pooling as well. This was traditionally handled by manually maintaining database connections, but as expected, that meant very well-crafted programming as the framework for pooling is highly complex. In recent years, things have become a lot easier due to availability of third-party libraries that allow connection pooling as well as SQL statement pooling, thus giving high performance in database intensive applications.

Various parameters such as number of minimum connections, maximum connections and idle connections can be set to make sure the connection pool works well according to the environment it is deployed to work in.