Transactional-consistent cache for database objects

1. A computer-implemented method comprising:

receiving new data by a cache manager implemented by one or more processors;

updating, by the cache manager, an entry of a cache with the new data received by the cache manager;

registering the updating of the entry with the new data with an invalidator implemented by one or more processors, the registering comprising a timestamp;

registering dependencies for the entry of the cache with the new data;

generating an invalidation event by the invalidator, the invalidation event including a notification about the updating of the entry of the cache with the new data received by the cache manager according to the timestamp; and

amortizing invalidation across a plurality of updates by not invalidating, by the cache manager, all entries dependent upon the updated entry immediately when the entry is updated and by invalidating, by the cache manager, an entry dependent upon the updated entry in response to a lookup of the entry dependent upon the updated entry.

2. The method in accordance with claim 1 , wherein a structure of the cache is configurable.

3. The method in accordance with claim 2 , wherein the structure of the cache includes a key and a value for each entry.

4. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

receive new data by a cache manager;

update, by the cache manager, an entry of a cache with the new data received by the cache manager;

register the updating of the entry with the new data with an invalidator, the registering comprising a timestamp;

register dependencies for the entry of the cache with the new data;

generate an invalidation event by the invalidator, the invalidation event including a notification about the updating of the entry of the cache with the new data received by the cache manager according to the timestamp; and

amortize invalidation across a plurality of updates by not invalidating, by the cache manager, all entries dependent upon the updated entry immediately when the entry is updated and by invalidating, by the cache manager, an entry dependent upon the updated entry in response to a lookup of the entry dependent upon the updated entry.

5. The computer program product in accordance with claim 4 , wherein a structure of the cache is configurable.

6. The computer program product in accordance with claim 5 , wherein the structure of the cache includes a key and a value for each entry.

7. A system comprising:

at least one programmable processor associated with an application server; and

a machine-readable medium storing instructions that, when executed by the at least one processor, cause the at least one programmable processor to perform operations comprising:

receive new data into a cache associated with the machine-readable medium;

update an entry of a cache with the new data;

register the updating of the entry with the new data, the registering comprising a timestamp;

register dependencies for the entry of the cache with the new data;

generate an invalidation event, the invalidation event including a notification about the updating of the entry of the cache with the new data received by the cache manager according to the timestamp; and

amortize invalidation across a plurality of updates by not invalidating, by the cache manager, all entries dependent upon the updated entry immediately when the entry is updated and by invalidating, by the cache manager, an entry dependent upon the updated entry in response to a lookup of the entry dependent upon the updated entry.

8. The system in accordance with claim 7 , wherein a structure of the cache is configurable.

9. The system in accordance with claim 8 , wherein the structure of the cache includes a key and a value for each entry.

10. The method in accordance with claim 1 , wherein invalidating the dependent entry in response to a lookup of the dependent entry occurs when a timestamp of the dependent entry is different from a current value of an internal counter.

11. The computer program product in accordance with claim 4 , wherein invalidating the dependent entry in response to a lookup of the dependent entry occurs when a timestamp of the dependent entry is different from a current value of an internal counter.

12. The system in accordance with claim 7 , wherein invalidating the dependent entry in response to a lookup of the dependent entry occurs when a timestamp of the dependent entry is different from a current value of an internal counter.