Cache data validation

• US 10,320,935 B2
• Filed: 01/28/2015
• Issued: 06/11/2019
• Est. Priority Date: 01/28/2015
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Slavicek, Pavel, Svoboda, Rostislav
• Primary Examiner(s): Lai, Michael C
• Application Number:
  US14/607,481
• Publication Number:
  US 20160219123A1
• Time in Patent Office: 1,595 Days
• Field of Search: 709201-204, 709217, 709221
• CPC Class Codes: G06F 12/0808 with cache invalidating means G06F12/0815 takes precedence
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 2212/608 Details relating to cache mapping
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

A method includes, with a computing system, receiving a first resource request for a Representational State Transfer (REST) web service, in response to determining that a resource request result of the first resource request is not cached, passing the first resource request to the REST web service, receiving from the REST web service, the resource request result and metadata associated with the resource request result, the metadata indicating a set of entities associated with the resource request result, caching the result and storing the metadata with the cached result, receiving a second resource request, the second resource request being the same as the first resource request, in response to determining that an entity from the set of entities has changed since the resource request result was cached, invalidating the cached resource request result and passing the first resource request to the REST web service.

Claims

1. A method performed by a computing system, the method comprising:

with the computing system, caching, within a cache module of the computing system, a resource request result from a Representational State Transfer (REST) web service;

with the computing system, storing, within an entity register, metadata associated with the resource request result, the metadata including a set of entities used to produce the resource request result, wherein the metadata further includes a version of each entity associated with the resource request result and accessibility of each entity associated with the resource request result;

with the computing system, receiving from a client, a first resource request for the REST web service, the first resource request corresponding to the resource request result;

with the computing system, in response to determining that the resource request result is cached within the cache module, checking, within the entity register, metadata associated with the resource request result; and

with the computing system, in response to determining that an entity from the set of entities has changed since the resource request result was cached, invalidating the cached resource request result and passing the first resource request to the REST web service, wherein determining that the entity from the set of entities has changed comprises checking the entity register to determine that a version of the entity has changed.

2. The method of claim 1, further comprising, in response to determining that all entities within the set of entities used to produce the resource request result have not changed since the resource request result was cached, returning the resource request result to the client.

3. The method of claim 1, further comprising:

with the computing system, receiving a second resource request; and

with the computing system, in response to determining that a result from the second resource request is not cached within the cache module, passing the second resource request to the REST web service.

4. The method of claim 1, with the computing system, receiving an update for the entity register from a persistence layer of the REST web service, the update indicating that an entity referenced within the entity register has changed.

5. The method of claim 4, further comprising, invalidating all cached results associated with the entity.

6. The method of claim 4, wherein determining that an entity from the set of entities has changed utilizes a monitoring module implemented with aspect oriented programming (AOP), the monitoring module configured to monitor the persistence layer.

7. The method of claim 1, wherein the resource request comprises a Universal Resource Identifier (URI).

8. The method of claim 1, wherein the computing system is configured to also provide the REST web service.

9. The method of claim 1, wherein the computing system is separate from and in communication with a computing system that provides the REST web service.

10. A system comprising:

a Representational State Transfer (REST) web service; and

a cache module configured to;

cache a resource request result from the REST web service;

store within an entity register associated with the cache module, metadata for the resource request result, the metadata including a set of entities used to produce the resource request result, wherein the metadata further includes a version of each entity associated with the resource request result and accessibility of each entity associated with the resource request result;

receive from a client, a first resource request for the REST web service, the first resource request corresponding to the resource request result;

in response to determining that the resource request result is cached within the cache module, check, within the entity register, the metadata used to produce the resource request result; and

in response to determining that an entity from the set of entities has changed since the resource request result was cached, invalidate the cached resource request result and passing the first resource request to the REST web service, wherein determining that the entity from the set of entities has changed comprises checking the entity register to determine that a version of the entity has changed.

11. The system of claim 10, wherein the cache module is further configured to, in response to determining that all entities within the set of entities used to produce the resource request result have not changed since the resource request result was cached, return the resource request result to the client.

12. The system of claim 10, wherein the cache module is further configured to:

receive a second resource request; and

in response to determining that a result from the second resource request is not cached within the cache module, pass the second resource request to the REST web service.

13. The system of claim 10, wherein the cache module is further configured to receive an update for the entity register from a persistence layer of the REST web service, the update indicating that an entity referenced within the entity register has changed.

14. The system of claim 13, wherein the cache module is further configured to invalidate all cached results associated with the entity.

15. The system of claim 13, further comprising, a monitoring module implemented with aspect oriented programming (AOP), the monitoring module configured to monitor the persistence layer.