Salesforce Com, Inc.

Sameer Khan

Sanjaya Lai

Francis James Leahy, Iii

Balaji Iyer

A request for a write action to be perform a data entity persisted in primary data sources is received. It is determined whether data changes to the data entity are tracked based on an object version key (OVK) definition of a target data object type. If the data changes to the data entity are tracked based on the OVK definition, an OVK key is generated, based on the OVK definition, from data field values specified in the request for the write action. An OVK version number for the data entity is updated, the OVK version number being identified by the OVK key. A cached data object of the target data object type is caused to be invalidated by the updated OVK version number, the cached data object of the target data object type being derived based on underlying data in the data entity persisted in the primary data sources.

Invalidating cached data objects in write-through operations

A request for retrieving a cached data object from a data object cache used to cached data objects retrieved from one or more primary data sources is received from a data object requester. Responsive to determining that the cached data object in the data object cache is expired, it is determined whether the cached data object in the data object cache is still within an extended time period. If the cached data object in the data object cache is still within an extended time period, it is determined whether the cached data object is free of a cache invalidity state change caused by a data change operation. If the cached data object is free of a cache invalidity state change, the cached data object is returned to the data object requester.

Extending usages of cached data objects beyond cache expiration periods

A read request for a counter designated to be only cached in a global cache is received. The counter is excluded from being persisted in and retrieved from one or more primary data sources It is determined whether the counter has already been created in the global cache. If the counter has already been created in the global cache, the counter is created in the global cache with an initial counter value while continually excluding the counter from being persisted in and retrieved from the one or more primary data sources. The counter is cached with a time-to-live (TTL) time period. The time-to-live time period is to be renewed on each subsequent read request of the counter. The counter is temporally stored in the data object cache until the TTL time period lapses.

Counter tracker service

A read request for a data object is received from a first processing thread. Responsive to the read request, it is determined whether a cached version of the data object is available from a global cache. If the cached version of the data object is not available from the global cache, a result is immediately returned to the first processing thread to indicate that the data object is not available from the global cache. The first processing thread is freed from waiting for the data object to become available from the global cache. A cache refresh message is enqueued, for the data object, in a message queue to cause a second different processing thread to subsequently dequeue the cache refresh message for the data object and build the data object in the global cache using underlying data persisted in and retrieved from a primary data source among the one or more primary data sources.

Growing community of inventors

Austin, TX, United States of America

Sameer Khan