Application vs Base Database Connection Pool

Situation: I have a requirement to use a connection pool when connecting to an Oracle database in python. Several python applications will use the auxiliary connection libraries that I am developing.

My thinking process: Here I can present two ways of pooling: 1) Let the connection pool be maintained and managed by the database itself (as provided by Oracle DRCP), and the calling modules simply request connections from the connection broker described by Oracle DRCP.

2) Is there a server process that manages the connection pool, and all the caller modules request connections from this pool (for example, dbcp?)

What suggestions do I need: option 1) looks very straightforward, since the pool should not be stored by the application. But I wanted to know what benefits I get, besides simplicity, with option 1)? I am trying to avoid option 2), as this will require a continuous dedicated server process (given that the racks are not suitable for connection objects). Is there another way?

+4
source share
1 answer

Let the database process the pool. It is smarter than you, and you will use every bug fix / performance improvement set by the Oracle database.

0
source

All Articles