Method and system for reducing connections to a database
A system automatically maintains a plurality of client connections associated with a plurality of clients, the plurality of client connections including active and idle connections. A first server receives a request from a client of the plurality of clients to access a second server of a plurality of second servers communicatively coupled to the first server, the plurality of second servers having varying communication protocols. The first server then identifies a first communication protocol associated with the second server and activating a link between the first server and the second server using the first communication protocol.
1. A computer-implemented method of managing database connections, the computer-implemented method comprising:
receiving an API call to establish a connection pool;
in response to the API call, establishing the connection pool that includes one or more reusable connections;
receiving a pool configuration parameter to limit the connection pool to a database within a geographical location associated with one or more application servers; and
reconfiguring, at runtime, the connection pool to be only connected to the one or more application servers associated with the geographical location.
2. The method of claim 1 , further comprising:
providing, via an API, a report including statistics associated with the connection pool.
3. The method of claim 2 , wherein the statistics include at least one of a current pool size, a current prepared statement cache size, a prepared statement cache eviction count, a thread wait for connection count, a thread wait for connection timeout count, a running average wait for connection time, a connection orphan count, a created connection count, or a destroyed connection count.
4. The method of claim 2 , further comprising:
providing for configuration of logging of the statistics.
5. The method of claim 1 , further comprising:
providing an API to flush one or more connections from the connection pool.
6. The method of claim 1 , further comprising:
providing for configuration of a query statement cache size.
7. The method of claim 1 , further comprising:
providing an API to return a connection object with vendor specific methods.
8. A system comprising:
one or more hardware processors; and
a non-transitory machine-readable medium for storing instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising:
receiving an API call to establish a connection pool;
in response to the API call, establishing the connection pool that includes one or more reusable connections;
receiving a pool configuration parameter to limit the connection pool to a database within a geographical location associated with one or more application servers; and
reconfiguring, at runtime, the connection pool to be only connected to the one or more application servers associated with the geographical location.
9. The system of claim 8 , wherein the operations further comprise:
providing, via an API, a report including statistics associated with the connection pool.
10. The system of claim 9 , wherein the statistics include at least one of a current pool size, a current prepared statement cache size, a prepared statement cache eviction count; a thread wait for connection count, a thread wait for connection timeout count, a running average wait for connection time, a connection orphan count, a created connection count, or a destroyed connection count.
11. The system of claim 9 , wherein the operations further comprise:
providing for configuration of logging of the statistics.
12. The system of claim 8 , wherein the operations further comprise:
providing an API to flush one or more connections from the connection pool.
13. The system of claim 8 , wherein the operations further comprise:
providing for configuration of a query statement cache size.
14. The system of claim 8 , wherein the operations further comprise:
providing an API to return a connection object with vendor specific methods.
15. A non-transitory machine-readable medium for storing instructions that, when executed by one or more hardware processors, cause the one or more hardware processors to perform operations comprising:
receiving an API call to establish a connection pool;
in response to the API call, establishing the connection pool that includes one or more reusable connections;
receiving a pool configuration parameter to limit the connection pool to a database within a geographical location associated with one or more application servers; and
reconfiguring, at runtime, the connection pool to be only connected to the one or more application servers associated with the geographical location.
16. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:
providing, via an API, a report including statistics associated with the connection pool.
17. The non-transitory machine-readable medium of claim 16 , wherein the statistics include at least one of a current pool size, a current prepared statement cache size, a prepared statement cache eviction count, a thread wait for connection count, a thread wait for connection timeout count, a running average wait for connection time, a connection orphan count, a created connection count, or a destroyed connection count.
18. The non-transitory machine-readable medium of claim 16 , wherein the operations further comprise:
providing for configuration of logging of the statistics.
19. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:
providing an API to flush one or more connections from the connection pool.
20. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:
providing for configuration of a query statement cache size.