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 method comprising:
establishing a connection pool based on a pool configuration parameter that limits the connection pool to a database within a geographical location;
receiving a request to update the pool configuration parameter; and
reconfiguring, at runtime, the connection pool based on the updated pool configuration parameter.
2. The method of claim 1 , wherein the connection pool comprises one or more reusable connections.
3. The method of claim 1 , further comprising:
reconfiguring, at the runtime, the connection pool to be only connected to one or more application servers associated with the geographical location based on the pool configuration parameter.
4. The method of claim 1 , further comprising:
generating a report that includes statistics associated with the connection pool.
5. The method of claim 4 , wherein the statistics comprises 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.
6. The method of claim 1 , further comprising:
providing an API to flush one or more connections from the connection pool.
7. The method of claim 6 , further comprising:
receiving an API request to flush the one or more connections from the connection pool; and
flushing, at the runtime, the one or more connections from the connection pool.
8. The method of claim 1 , further comprising:
receiving a further API request to flush a query statement from a query statement cache associated with a reusable connection in the connection pool; and
in response to receiving the further API request, flushing the query statement from the query statement cache.
9. The method of claim 1 , further comprising:
providing a further API to return a connection object with a vendor-specific method.
10. 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:
establishing a connection pool based on a pool configuration parameter that limits the connection pool to a database within a geographical location;
receiving a request to update the pool configuration parameter; and
reconfiguring, at runtime, the connection pool based on the updated pool configuration parameter.
11. The system of claim 10 , wherein the connection pool comprises one or more reusable connections.
12. The system of claim 10 , wherein the operations further comprise:
reconfiguring, at the runtime, the connection pool to be only connected to one or more application servers associated with the geographical location based on the pool configuration parameter.
13. The system of claim 10 , wherein the operations further comprise:
generating a report that includes statistics associated with the connection pool.
14. The system of claim 13 , wherein the statistics comprises 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.
15. The system of claim 10 , wherein the operations further comprise:
providing an API to flush one or more connections from the connection pool.
16. The system of claim 15 , wherein the operations further comprise:
receiving an API request to flush the one or more connections from the connection pool; and
flushing, at the runtime, the one or more connections from the connection pool.
17. The system of claim 10 , wherein the operations further comprise:
receiving a further API request to flush a query statement from a query statement cache associated with a reusable connection in the connection pool; and
in response to receiving the further API request, flushing the query statement from the query statement cache.
18. 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:
establishing a connection pool based on a pool configuration parameter that limits the connection pool to a database within a geographical location;
receiving a request to update the pool configuration parameter; and
reconfiguring, at runtime, the connection pool based on the updated pool configuration parameter.