Interface Cache
- All Known Implementing Classes:
AbstractValueAdaptingCache,CaffeineCache,ConcurrentMapCache,JCacheCache,NoOpCache,TransactionAwareCacheDecorator
Serves primarily as an SPI for Spring's annotation-based caching
model (Cacheable and co)
and secondarily as an API for direct usage in applications.
Note: Due to the generic use of caching, it is recommended
that implementations allow storage of null values
(for example to cache methods that return null).
- Since:
- 3.1
- Author:
- Costin Leau, Juergen Hoeller, Stephane Nicoll
- See Also:
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic classWrapper exception to be thrown fromget(Object, Callable)in case of the value loader callback failing with an exception.static interfaceA (wrapper) object representing a cache value. -
Method Summary
Modifier and TypeMethodDescriptionvoidclear()Clear the cache through removing all mappings.voidEvict the mapping for this key from this cache if it is present.default booleanevictIfPresent(Object key) Evict the mapping for this key from this cache if it is present, expecting the key to be immediately invisible for subsequent lookups.Return the value to which this cache maps the specified key.<T> TReturn the value to which this cache maps the specified key, generically specifying a type that return value will be cast to.<T> TReturn the value to which this cache maps the specified key, obtaining that value fromvalueLoaderif necessary.getName()Return the cache name.Return the underlying native cache provider.default booleanInvalidate the cache through removing all mappings, expecting all entries to be immediately invisible for subsequent lookups.voidAssociate the specified value with the specified key in this cache.default Cache.ValueWrapperputIfAbsent(Object key, Object value) Atomically associate the specified value with the specified key in this cache if it is not set already.default CompletableFuture<?>Return the value to which this cache maps the specified key, wrapped in aCompletableFuture.default <T> CompletableFuture<T>retrieve(Object key, Supplier<CompletableFuture<T>> valueLoader) Return the value to which this cache maps the specified key, obtaining that value fromvalueLoaderif necessary.
-
Method Details
-
getName
String getName()Return the cache name. -
getNativeCache
Object getNativeCache()Return the underlying native cache provider. -
get
Return the value to which this cache maps the specified key.Returns
nullif the cache contains no mapping for this key; otherwise, the cached value (which may benullitself) will be returned in aCache.ValueWrapper.- Parameters:
key- the key whose associated value is to be returned- Returns:
- the value to which this cache maps the specified key,
contained within a
Cache.ValueWrapperwhich may also hold a cachednullvalue. A straightnullbeing returned means that the cache contains no mapping for this key. - See Also:
-
get
Return the value to which this cache maps the specified key, generically specifying a type that return value will be cast to.Note: This variant of
getdoes not allow for differentiating between a cachednullvalue and no cache entry found at all. Use the standardget(Object)variant for that purpose instead.- Parameters:
key- the key whose associated value is to be returnedtype- the required type of the returned value (may benullto bypass a type check; in case of anullvalue found in the cache, the specified type is irrelevant)- Returns:
- the value to which this cache maps the specified key
(which may be
nullitself), or alsonullif the cache contains no mapping for this key - Throws:
IllegalStateException- if a cache entry has been found but failed to match the specified type- Since:
- 4.0
- See Also:
-
get
Return the value to which this cache maps the specified key, obtaining that value fromvalueLoaderif necessary. This method provides a simple substitute for the conventional "if cached, return; otherwise create, cache and return" pattern.If possible, implementations should ensure that the loading operation is synchronized so that the specified
valueLoaderis only called once in case of concurrent access on the same key.If the
valueLoaderthrows an exception, it is wrapped in aCache.ValueRetrievalException- Parameters:
key- the key whose associated value is to be returned- Returns:
- the value to which this cache maps the specified key
- Throws:
Cache.ValueRetrievalException- if thevalueLoaderthrows an exception- Since:
- 4.3
- See Also:
-
retrieve
Return the value to which this cache maps the specified key, wrapped in aCompletableFuture. This operation must not block but is allowed to return a completedCompletableFutureif the corresponding value is immediately available.Can return
nullif the cache can immediately determine that it contains no mapping for this key (for example, through an in-memory key map). Otherwise, the cached value will be returned in theCompletableFuture, withnullindicating a late-determined cache miss. A nestedCache.ValueWrapperpotentially indicates a nullable cached value; the cached value may also be represented as a plain element if null values are not supported. Calling code needs to be prepared to handle all those variants of the result returned by this method.- Parameters:
key- the key whose associated value is to be returned- Returns:
- the value to which this cache maps the specified key, contained
within a
CompletableFuturewhich may also be empty when a cache miss has been late-determined. A straightnullbeing returned means that the cache immediately determined that it contains no mapping for this key. ACache.ValueWrappercontained within theCompletableFutureindicates a cached value that is potentiallynull; this is sensible in a late-determined scenario where a regular CompletableFuture-containednullindicates a cache miss. However, a cache may also return a plain value if it does not support the actual caching ofnullvalues, avoiding the extra level of value wrapping. Spring's cache processing can deal with all such implementation strategies. - Since:
- 6.1
- See Also:
-
retrieve
Return the value to which this cache maps the specified key, obtaining that value fromvalueLoaderif necessary. This method provides a simple substitute for the conventional "if cached, return; otherwise create, cache and return" pattern, based onCompletableFuture. This operation must not block.If possible, implementations should ensure that the loading operation is synchronized so that the specified
valueLoaderis only called once in case of concurrent access on the same key.Null values always indicate a user-level
nullvalue with this method. The providedCompletableFuturehandle produces a value or raises an exception. If thevalueLoaderraises an exception, it will be propagated to the returnedCompletableFuturehandle.- Parameters:
key- the key whose associated value is to be returned- Returns:
- the value to which this cache maps the specified key, contained
within a
CompletableFuturewhich will never benull. The provided future is expected to produce a value or raise an exception. - Since:
- 6.1
- See Also:
-
put
Associate the specified value with the specified key in this cache.If the cache previously contained a mapping for this key, the old value is replaced by the specified value.
Actual registration may be performed in an asynchronous or deferred fashion, with subsequent lookups possibly not seeing the entry yet. This may for example be the case with transactional cache decorators. Use
putIfAbsent(java.lang.Object, java.lang.Object)for guaranteed immediate registration.If the cache is supposed to be compatible with
CompletableFutureand reactive interactions, the put operation needs to be effectively non-blocking, with any backend write-through happening asynchronously. This goes along with a cache implemented and configured to supportretrieve(Object)andretrieve(Object, Supplier).- Parameters:
key- the key with which the specified value is to be associatedvalue- the value to be associated with the specified key- See Also:
-
putIfAbsent
Atomically associate the specified value with the specified key in this cache if it is not set already.This is equivalent to:
except that the action is performed atomically. While all out-of-the-boxValueWrapper existingValue = cache.get(key); if (existingValue == null) { cache.put(key, value); } return existingValue;CacheManagerimplementations are able to perform the put atomically, the operation may also be implemented in two steps, for example, with a check for presence and a subsequent put, in a non-atomic way. Check the documentation of the native cache implementation that you are using for more details.The default implementation delegates to
get(Object)andput(Object, Object)along the lines of the code snippet above.- Parameters:
key- the key with which the specified value is to be associatedvalue- the value to be associated with the specified key- Returns:
- the value to which this cache maps the specified key (which may be
nullitself), or alsonullif the cache did not contain any mapping for that key prior to this call. Returningnullis therefore an indicator that the givenvaluehas been associated with the key. - Since:
- 4.1
- See Also:
-
evict
Evict the mapping for this key from this cache if it is present.Actual eviction may be performed in an asynchronous or deferred fashion, with subsequent lookups possibly still seeing the entry. This may for example be the case with transactional cache decorators. Use
evictIfPresent(java.lang.Object)for guaranteed immediate removal.If the cache is supposed to be compatible with
CompletableFutureand reactive interactions, the evict operation needs to be effectively non-blocking, with any backend write-through happening asynchronously. This goes along with a cache implemented and configured to supportretrieve(Object)andretrieve(Object, Supplier).- Parameters:
key- the key whose mapping is to be removed from the cache- See Also:
-
evictIfPresent
Evict the mapping for this key from this cache if it is present, expecting the key to be immediately invisible for subsequent lookups.The default implementation delegates to
evict(Object), returningfalsefor not-determined prior presence of the key. Cache providers and in particular cache decorators are encouraged to perform immediate eviction if possible (for example, in case of generally deferred cache operations within a transaction) and to reliably determine prior presence of the given key.- Parameters:
key- the key whose mapping is to be removed from the cache- Returns:
trueif the cache was known to have a mapping for this key before,falseif it did not (or if prior presence could not be determined)- Since:
- 5.2
- See Also:
-
clear
void clear()Clear the cache through removing all mappings.Actual clearing may be performed in an asynchronous or deferred fashion, with subsequent lookups possibly still seeing the entries. This may for example be the case with transactional cache decorators. Use
invalidate()for guaranteed immediate removal of entries.If the cache is supposed to be compatible with
CompletableFutureand reactive interactions, the clear operation needs to be effectively non-blocking, with any backend write-through happening asynchronously. This goes along with a cache implemented and configured to supportretrieve(Object)andretrieve(Object, Supplier).- See Also:
-
invalidate
default boolean invalidate()Invalidate the cache through removing all mappings, expecting all entries to be immediately invisible for subsequent lookups.- Returns:
trueif the cache was known to have mappings before,falseif it did not (or if prior presence of entries could not be determined)- Since:
- 5.2
- See Also:
-