Distributed Consistent Grid of In-Memory Database Caches

• US 20110072217A1
• Filed: 09/18/2009
• Published: 03/24/2011
• Est. Priority Date: 09/18/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Thomas, Dilys, Hoang, Chi, Neimat, Marie-Anne, Bandi, Nagender, Cheng, Susan, Miller, John, Wang, Chih-Ping, Lahiri, Tirthankar
• Granted Patent: US 8,401,994 B2
• Time in Patent Office: Days
• US Class Current: 711/130
• CPC Class Codes: G06F 12/084 with a shared cache
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures

Abstract

A plurality of mid-tier databases form a single, consistent cache grid for data in a one or more backend data sources, such as a database system. The mid-tier databases may be standard relational databases. Cache agents at each mid-tier database swap in data from the backend database as needed. Consistency in the cache grid is maintained by ownership locks. Cache agents prevent database operations that will modify cached data in a mid-tier database unless and until ownership of the cached data can be acquired for the mid-tier database. Cache groups define what backend data may be cached, as well as a general structure in which the backend data is to be cached. Metadata for cache groups is shared to ensure that data is cached in the same form throughout the entire grid. Ownership of cached data can then be tracked through a mapping of cached instances of data to particular mid-tier databases.

Claims

1. A method comprising:

maintaining a grid of mid-tier databases storing cache instances of elements from one or more one or more backend data sources, wherein changes to said cache instances are propagated back to the one or more backend data sources;

receiving a request to change data in a particular mid-tier database, said data belonging to a particular element in the one or more backend data sources;

in response to the request;

identifying a particular cache instance mapped to the data;

determining ownership information for the particular cache instance, wherein the ownership information indicates either;

a) a mid-tier database to which the particular cache instance has been exclusively assigned, or b) that the particular cache instance is not yet stored in the grid;

changing the data in the particular mid-tier database only if the particular database has been assigned exclusive ownership of the particular cache instance;

wherein the method is performed by one or more computing devices implementing the grid.

2. The method of claim 1, further comprising waiting to perform the step of changing the data in the particular mid-tier database until said ownership information indicates that the particular database has exclusive ownership of the particular cache instance.

3. The method of claim 2, further comprising:

determining that another mid-tier database in the grid stores the particular cache instance;

causing the any pending transactions relating to the particular cache instance to be committed at the other mid-tier database;

transmitting the particular cache instance from the other mid-tier database to the particular mid-tier database.

4. The method of claim 1, wherein, for any given element at any given time, the grid of mid-tier databases stores only a single cache instance corresponding to the element, wherein determining ownership information comprises determining if the particular mid-tier database stores the particular cache instance.

5. The method of claim 1, wherein the steps of identifying the particular cache instance and determining ownership information comprise:

determining whether the particular mid-tier database stores a cache instance corresponding to the particular element;

upon said determining, if the particular mid-tier database stores the cache instance corresponding to the particular element;

identifying the cache instance as the particular cache instance;

determining that the particular mid-tier database has been assigned exclusive ownership of the particular cache instance;

upon said determining, if the particular mid-tier database does not store the cache instance corresponding to the particular element;

determining whether any other mid-tier database in the grid stores the cache instance corresponding to the particular element;

upon determining whether any other mid-tier database in the grid stores the cache instance, if an other mid-tier database stores the cache instance corresponding to the particular element;

moving the cache instance from the other mid-tier database to the particular mid-tier database;

upon determining whether any other mid-tier database in the grid stores the cache instance, if no other mid-tier database stores the cache instance corresponding to the particular element;

generating the particular cache instance for the particular element;

storing the particular cache instance at the particular mid-tier database;

upon storing the particular cache instance at the particular mid-tier database, determining that the particular mid-tier database has been assigned exclusive ownership of the particular cache instance.

6. The method of claim 1, wherein determining the ownership information comprises accessing shared ownership metadata mapping said cache instances to said mid-tier databases.

7. The method of claim 1, wherein the mid-tier databases are relational databases.

8. The method of claim 1,

wherein access to the one or more backend data sources is provided by a database server;

wherein said database server is configured to respond to database statements pertaining to data in the one or more backend data sources from multiple clients, the multiple clients including at least one client executing at a computing device that does not implement the mid-tier database;

wherein said database server does not provide access to said mid-tier databases;

wherein the request to change data in the mid-tier database is a database statement.

9. The method of claim 1, further comprising:

maintaining metadata defining one or more shared cache groups, the one or more shared cache groups comprising said cache instances, said metadata indicating that at any given time, the grid should maintain only a single consistent version of each of said cache instances;

wherein the particular mid-tier database stores one or more cache instances that are not in the one or more grid cache groups;

receiving a second request to change second data in the particular mid-tier database, said second data belonging to a second particular element in the one or more backend data sources;

based on said metadata, determining that the second particular element does not pertain to any of the one or more grid cache groups, and therefore changing a second cache instance corresponding to the second particular element without any determination of exclusive ownership.

10. The method of claim 9,

wherein each of the one or more grid cache groups is mapped to a different set of one or more tables in the one or more backend data sources;

wherein no table in the one or more backend data sources is mapped to more than one of the one or more grid cache groups;

wherein each cache instance of said cache instances maps to a different set of one or more associated rows or row portions.

11. The method of claim 1, wherein the one or more computing devices store an active copy of the particular mid-tier database and a standby copy of the particular mid-tier database, wherein upon failure of the active copy of the particular mid-tier database, the standby copy of the particular mid-tier database retains ownership of any cache instances assigned to the particular mid-tier database.

12. The method of claim 1, wherein each mid-tier database is stored in a volatile memory at the one or more computing devices.

13. The method of claim 1, wherein, at the time of the request, the particular cache instance is stored at both the particular mid-tier database and a second mid-tier database, the method further comprising, in response to the request, updating the ownership information to indicate that the particular mid-tier database owns the particular cache instance.

14. The method of claim 13,

wherein the request is a first request;

wherein the method further comprises;

prior to the first request, receiving a second request to read said data from the particular mid-tier database cache;

reading the data from the particular cache instance at the particular mid-tier database without the ownership information indicating that the particular mid-tier database owns the particular cache instance.

15. The method of claim 1, further comprising propagating changes in the backend data source to the plurality of mid-tier databases.

16. A system comprising:

one or more backend data sources stored in at least one persistent storage device;

a backend server executing at a first set of one or more computing devices, the backend server being configured to provide access to the one or more backend data sources;

a plurality of mid-tier databases stored at a second set of one or more computing devices;

one or more processes executing at the second set of computing devices, the one or more processes configured to maintain, in the plurality of mid-tier databases, a caching grid, said caching grid comprising at least a plurality of shared cache instances of data from the one or more backend data sources;

wherein the plurality of shared cache instances are stored in the plurality of mid-tier databases;

wherein the one or more processes ensure that for any given data element of the one or more backend data sources for which the caching grid maintains a shared cache instance, the plurality of mid-tier databases store, at any given time, no more than one version of the shared cache instance.

17. The system of claim 16, wherein the one or more processes are further configured to maintain the caching grid in an online state even after the failure of one or more of the plurality of mid-tier databases.

18. One or more storage media storing instructions which, when executed by one or more computing devices, cause performance of:

maintaining a grid of mid-tier databases storing cache instances of elements from one or more one or more backend data sources, wherein changes to said cache instances are propagated back to the one or more backend data sources;

receiving a request to change data in a particular mid-tier database, said data belonging to a particular element in the one or more backend data sources;

in response to the request;

identifying a particular cache instance mapped to the data;

determining ownership information for the particular cache instance, wherein the ownership information indicates either;

a) a mid-tier database to which the particular cache instance has been exclusively assigned, or b) that the particular cache instance is not yet stored in the grid;

changing the data in the particular mid-tier database only if the particular database has been assigned exclusive ownership of the particular cache instance;

wherein the method is performed by one or more computing devices implementing the grid.

19. The one or more storage media of claim 18, wherein the instructions, when executed by one or more computing devices, further cause performance of:

waiting to perform the step of changing the data in the particular mid-tier database until said ownership information indicates that the particular database has exclusive ownership of the particular cache instance.

20. The one or more storage media of claim 19, wherein the instructions, when executed by one or more computing devices, further cause performance of:

determining that another mid-tier database in the grid stores the particular cache instance;

causing the any pending transactions relating to the particular cache instance to be committed at the other mid-tier database;

transmitting the particular cache instance from the other mid-tier database to the particular mid-tier database.

21. The one or more storage media of claim 18, wherein, for any given element at any given time, the grid of mid-tier databases stores only a single cache instance corresponding to the element, wherein determining ownership information comprises determining if the particular mid-tier database stores the particular cache instance.

22. The one or more storage media of claim 18, wherein identifying the particular cache instance and determining ownership information comprise:

determining whether the particular mid-tier database stores a cache instance corresponding to the particular element;

upon said determining, if the particular mid-tier database stores the cache instance corresponding to the particular element;

identifying the cache instance as the particular cache instance;

determining that the particular mid-tier database has been assigned exclusive ownership of the particular cache instance;

upon said determining, if the particular mid-tier database does not store the cache instance corresponding to the particular element;

determining whether any other mid-tier database in the grid stores the cache instance corresponding to the particular element;

upon determining whether any other mid-tier database in the grid stores the cache instance, if an other mid-tier database stores the cache instance corresponding to the particular element;

moving the cache instance from the other mid-tier database to the particular mid-tier database;

upon determining whether any other mid-tier database in the grid stores the cache instance, if no other mid-tier database stores the cache instance corresponding to the particular element;

generating the particular cache instance for the particular element;

storing the particular cache instance at the particular mid-tier database;

upon storing the particular cache instance at the particular mid-tier database, determining that the particular mid-tier database has been assigned exclusive ownership of the particular cache instance.

23. The one or more storage media of claim 18, wherein determining the ownership information comprises accessing shared ownership metadata mapping said cache instances to said mid-tier databases.

24. The one or more storage media of claim 18, wherein the mid-tier databases are relational databases.

25. The one or more storage media of claim 18,

wherein access to the one or more backend data sources is provided by a database server;

wherein said database server is configured to respond to database statements pertaining to data in the one or more backend data sources from multiple clients, the multiple clients including at least one client executing at a computing device that does not implement the mid-tier database;

wherein said database server does not provide access to said mid-tier databases;

wherein the request to change data in the mid-tier database is a database statement.

26. The one or more storage media of claim 18, wherein the instructions, when executed by one or more computing devices, further cause performance of:

maintaining metadata defining one or more shared cache groups, the one or more shared cache groups comprising said cache instances, said metadata indicating that at any given time, the grid should maintain only a single consistent version of each of said cache instances;

wherein the particular mid-tier database stores one or more cache instances that are not in the one or more grid cache groups;

receiving a second request to change second data in the particular mid-tier database, said second data belonging to a second particular element in the one or more backend data sources;

based on said metadata, determining that the second particular element does not pertain to any of the one or more grid cache groups, and therefore changing a second cache instance corresponding to the second particular element without any determination of exclusive ownership.

27. The one or more storage media of claim 26,

wherein each of the one or more grid cache groups is mapped to a different set of one or more tables in the one or more backend data sources;

wherein no table in the one or more backend data sources is mapped to more than one of the one or more grid cache groups;

wherein each cache instance of said cache instances maps to a different set of one or more associated rows or row portions.

28. The one or more storage media of claim 18, wherein the one or more computing devices store an active copy of the particular mid-tier database and a standby copy of the particular mid-tier database, wherein upon failure of the active copy of the particular mid-tier database, the standby copy of the particular mid-tier database retains ownership of any cache instances assigned to the particular mid-tier database.

29. The one or more storage media of claim 18, wherein each mid-tier database is stored in a volatile memory at the one or more computing devices.

30. The one or more storage media of claim 18, wherein, at the time of the request, the particular cache instance is stored at both the particular mid-tier database and a second mid-tier database, the method further comprising, in response to the request, updating the ownership information to indicate that the particular mid-tier database owns the particular cache instance.

31. The one or more storage media of claim 30,

wherein the request is a first request;

wherein the instructions, when executed by one or more computing devices, further cause performance of;

prior to the first request, receiving a second request to read said data from the particular mid-tier database cache;

reading the data from the particular cache instance at the particular mid-tier database without the ownership information indicating that the particular mid-tier database owns the particular cache instance.

32. The one or more storage media of claim 18, wherein the instructions, when executed by one or more computing devices, further cause performance of:

propagating changes in the backend data source to the plurality of mid-tier databases.