Invalidating cached data using secondary keys

• US 20050120181A1
• Filed: 12/02/2003
• Published: 06/02/2005
• Est. Priority Date: 12/02/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Liu, Xiang, Zeng, Zheng, Ling, Shu, Jacobs, Lawrence, Goell, Fredric, Arunagirinathan, Senthilnathan, Zhu, Yuhui
• Granted Patent: US 7,076,608 B2
• Time in Patent Office: Days
• US Class Current: 711/133
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A system and method for facilitating the invalidation of cached data, in which the data to be invalidated are identified using information other than a primary key. The primary key for a cached data object, such as a web page, may be a Uniform Resource Locator (URL). Instead of using an object'"'"'s URL to identify to a cache the data to be invalidated, a secondary key is used, such as the object'"'"'s data source or a template from which the object was created. An application communicates the secondary key to a cache, and the cache identifies cached objects that match the secondary key. Those data objects are then invalidated without having to issue multiple invalidation messages from the application.

Claims

1. A method of using a secondary key to facilitate invalidation of cached data, comprising:

at a first data source;

associating a URL (Uniform Resource Locator) with a first data object;

forwarding the first data object to a cache, along with;

a primary key comprising the URL; and

a secondary key configured to identify the first data source;

caching the first data object at the cache;

issuing an invalidation message from the first data source to the cache, wherein said invalidation message comprises the identifier; and

at the cache, using the identifier to identify one or more data objects for invalidation, including the first data object.

2. The method of claim 1, wherein:

the primary key uniquely identifies the first data object; and

the secondary key identifies a set of data objects having the same data source.

3. The method of claim 1, further comprising, at the cache:

maintaining a mapping of said secondary key to URLs of the one or more data objects.

4. The method of claim 1, further comprising, at the cache:

maintaining a mapping of the URL of the first data object to one or more secondary keys of the first data object, including said secondary key.

5. The method of claim 1, wherein the invalidation message is issued after the source of the one or more data objects changes from the first data source to a second data source.

6. A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of using a secondary key to facilitate invalidation of cached data,- the method comprising:

at a first data source;

associating a URL (Uniform Resource Locator) with a first data object;

forwarding the first data object to a cache, along with;

a primary key comprising the URL; and

a secondary key configured to identify the first data source;

caching the first data object at the cache;

issuing an invalidation message from the first data source to the cache, wherein said invalidation message comprises the identifier; and

at the cache, using the identifier to identify one or more data objects for invalidation, including the first data object.

7. A computer-implemented method of facilitating invalidation of cached data using a secondary key, the method comprising:

at an application configured to produce cacheable data objects, associating with a first data object;

a first primary key configured to uniquely identify the first data object within a collection of computer systems; and

a first secondary key configured to identify multiple data objects having a common attribute;

when the first data object is provided to a cache to be cached, providing said first secondary key; and

issuing an invalidation message from the application to the cache to invalidate the multiple data objects, wherein the invalidation message includes said first secondary key.

8. The method of claim 7, wherein the first primary key is identified to the cache by a client when the client desires to receive the first data object.

9. The method of claim 8, wherein the first secondary key is not known to the client.

10. The method of claim 7, wherein said first secondary key comprises an identifier of the application.

11. The method of claim 7, wherein:

the common attribute is a data source; and

said first secondary key comprises an identifier of a source of the first data object.

12. The method of claim 7, wherein:

the common attribute is a template used to produce the multiple data objects; and

said first secondary key comprises an identifier of the template.

13. The method of claim 7, further comprising, at the cache:

receiving the invalidation message;

mapping said first secondary key to primary keys of the multiple data objects; and

invalidating the multiple data objects.

14. The method of claim 7, wherein said first secondary key comprises a security symbol.

15. The method of claim 7, wherein said first secondary key comprises a name.

16. The method of claim 7, wherein said first secondary key comprises a date.

17. The method of claim 7, wherein said first secondary key comprises address information.

18. The method of claim 7, wherein said first secondary key comprises a product identifier.

19. A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of facilitating invalidation of cached data using a secondary key, the method comprising:

at an application configured to produce cacheable data objects, associating with a first data object;

a first primary key configured to uniquely identify the first data object within a collection of computer systems; and

a first secondary key configured to identify multiple data objects having a common attribute;

when the first data object is provided to a cache to be cached, providing said first secondary key; and

issuing an invalidation message from the application to the cache to invalidate the multiple data objects, wherein the invalidation message includes said first secondary key.

20. A computer-implemented method of facilitating invalidation of cached data using a secondary key, the method comprising:

receiving at a cache a first data object to be cached, wherein the first data object is accompanied by;

a first primary key configured to uniquely identify the first data object within a network; and

a first secondary key comprising information common to multiple data objects in the network, including the first data object;

maintaining at the cache a mapping between said first secondary key and primary keys of the multiple data objects; and

in response to receipt at the cache of an invalidation message identifying said first secondary key;

identifying the primary keys of the multiple data objects; and

invalidating the multiple data objects.

21. The method of claim 20, wherein said invalidation message does not specify the primary keys of the multiple data objects.

22. The method of claim 20, wherein requests received at the cache to serve the first data object include the first primary key but not said first secondary key.

23. The method of claim 20, wherein said first secondary key comprises a security symbol.

24. The method of claim 20, wherein said first secondary key comprises a name.

25. The method of claim 20, wherein said first secondary key comprises a date.

26. The method of claim 20, wherein said first secondary key comprises address information.

27. The method of claim 20, wherein said first secondary key comprises a product identifier.

28. A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of facilitating invalidation of cached data using a secondary key, the method comprising:

receiving at a cache a first data object to be cached, wherein the first data object is accompanied by;

a first primary key configured to uniquely identify the first data object within a network; and

a first secondary key comprising information common to multiple data objects in the network, including the first data object;

maintaining at the cache a mapping between said first secondary key and primary keys of the multiple data objects; and

in response to receipt at the cache of an invalidation message identifying said first secondary key;

identifying the primary keys of the multiple data objects; and

invalidating the multiple data objects.

29. A system for facilitating invalidation of cached data objects, comprising:

a first cache configured to cache data objects for serving to clients; and

a data source, coupled to the first cache via a network, wherein the data source is configured to;

produce data objects for caching in the cache;

associate with each data object a primary key configured to uniquely identify the data object within the network;

associate with each data object a secondary key, wherein each secondary key is associated with a set of data objects having a common attribute; and

issue to the cache an invalidation message comprising a first secondary key to facilitate the invalidation of a first set of data objects.

30. The system of claim 29, wherein a client is configured to receive the primary key of a data object it desires, but not the secondary key.

31. The system of claim 29, wherein:

the first cache is configured to cache multiple versions of a first data object; and

each said version is cached with a different primary key and the same secondary key.

32. The system of claim 29, further comprising:

a second cache configured to cache a first data object cached by the first cache, with a different primary key and the same secondary key.