DEVICES FOR PROVIDING DISTRIBUTABLE MIDDLEWARE DATA PROXY BETWEEN APPLICATION SERVERS AND DATABASE SERVERS

• US 20100174939A1
• Filed: 05/29/2008
• Published: 07/08/2010
• Est. Priority Date: 06/05/2007
• Status: Active Grant

• Current Assignee: Safe Bed Technologies Company
• Original Assignee: Safe Bed Technologies Company
• Inventors: Vexler, Vladimir
• Granted Patent: US 8,849,793 B2
• Time in Patent Office: Days
• US Class Current: 714/5
• CPC Class Codes: G06F 16/24552 Database cache management

Abstract

The present invention discloses devices Including a transparent client-connection manager for exchanging client data between an application server and the device: a request analyzer for analyzing query requests from at least one application server; a data-retrieval/command-execution module for executing query requests; a database connection manager for exchanging database data between at least one database server and the device: a cache-memory pool for storing data items from at least one database server: a cache-policy module for determining cache criteria for storing the data Items In the cache-memory pool; and a data-consistency invalidation module for determining invalidated data Items based on invalidation criteria for removing from the cache-memory pool. The cache-memory pool Is configured to utilize memory modules residing in data proxy devices and distributed cache management utility, enabling the memory capacity to be used as a cluster to balance workloads.

Claims

1. A device for providing distributable middleware data proxy, the device comprising:

(a) a transparent client-connection manager for exchanging client data between at least one application server and the device;

(b) a request analyzer for analyzing query requests from said at least one application server;

(c) a data-retrieval/command-execution module for executing said query requests;

(d) a database-connection manager for exchanging database data between at least one database server and the device;

(e) a cache-memory pool for storing data items from said at least one database server;

(f) a cache-policy module for determining cache criteria for storing said data items in said cache-memory pool; and

(g) a data-consistency invalidation module for determining invalidated data items based on invalidation criteria for removing from said cache-memory pool.

2. The device of claim 1, wherein said request analyzer is configured for:

creating hashed query-specific keys of said query requests; and

(ii) identifying a query type of said query requests.

3. The device of claim 1, wherein said cache-memory pool is configured to utilize respective memory modules residing in a plurality of operationally-connected data-proxy devices.

4. The device of claim 3, the device further comprising:

(h) a distributed-cache management utility for managing memory capacity in said memory modules.

5. The device of claim 4, wherein said distributed-cache management utility enables said memory capacity to be utilized as a memory cluster in order to balance workloads of said memory capacity.

6. The device of claim 1, the device further comprising:

(h) a logger for logging details of said query requests.

7. The device of claim 6, wherein said details includes at least one detail selected from the group consisting of:

each said query request, a hashed query-specific key, a request type, a query date/time, client information, database-server details, data-retrieval source, cache type, data checksum, a data-retrieval date/time, a timestamp, client IP information, and query information.

8. The device of claim 1, the device further comprising:

(h) a database agent for;

monitoring data changes in said at least one database server; and

(ii) reporting said data changes to said data-consistency invalidation module.

9. The device of claim 1, the device further comprising:

(h) a failsafe utility for enabling an alternate data-proxy device, operationally connected to the device, to provide device functionality upon an occurrence of a device failure.

10. The device of claim 1, the device further comprising:

(h) a database load-balancer for load-balancing in said at least one database server.

11. The device of claim 1, the device further comprising:

(h) a special-procedures analyzer utility for parsing and analyzing executable code in said query requests.

12. The device of claim 1, wherein said cache criteria include at least one criterion selected from the group consisting of:

a query-request frequency, a data-change frequency, and an available cache-memory capacity.

13. The device of claim 1, wherein said data-retrieval/command-execution module is operative to activate triggers for detecting said invalidated data items.

14. The device of claim 1, wherein said invalidation criteria include at least one criterion selected from the group consisting of:

an update in said database data, a deletion in said database data, an insertion in said database data, an update in secondary database data referenced in said database data, a deletion in said secondary database data referenced in said database data, and an insertion in said secondary database data referenced in said database data.

15. The device of claim 1, wherein said request analyzer is configured for parsing said query requests.

16. The device of claim 15, wherein said parsing assists in identifying said invalidated data items.

17. A method for providing distributable middleware data proxy, the method comprising the steps of:

(a) transparently exchanging client data between at least one application server and a data-proxy device;

(b) analyzing query requests from said at least one application server;

(c) executing said query requests;

(d) exchanging database data between at least one database server and said data-proxy device;

(e) determining criteria for storing data items from said at least one database server in data-proxy device;

(f) storing said data items from said at least one database server in said data-proxy device; and

(g) determining invalidated data items for removing from said data-proxy device.

18. The method of claim 17, the method further comprising the step of:

(h) managing memory capacity in respective memory modules residing in a plurality of operationally-connected data-proxy devices.

19. The method of claim 18, wherein said step of managing includes utilizing said memory capacity as a memory cluster in order to balance workloads of said memory capacity.

20. The method of claim 17, the method further comprising the steps of:

(h) monitoring data changes in said at least one database server; and

(i) reporting said data changes to said data-proxy device.