anchor.diff:  interference to the invoker.
   
   IMPORTANT: This approach works only for methods that are guaranteed to return the same
  -output (result) for a given input (or arguments) no matter how many times it is invoked.
  +output (result) for a given input (or arguments) no matter how many times they are invoked.
   
   The caching abstraction provides other cache-related operations, such as the ability
   to update the content of the cache or to remove one or all entries. These are useful if
  
positive.code: `org.springframework.cache.Cache` and `org.springframework.cache.CacheManager` interfaces.
  
  Spring provides <<cache-store-configuration, a few implementations>> of that abstraction:
  JDK `java.util.concurrent.ConcurrentMap` based caches, https://www.ehcache.org/[Ehcache 2.x],
  Gemfire cache, https://github.com/ben-manes/caffeine/wiki[Caffeine], and JSR-107
  compliant caches (such as Ehcache 3.x). See <<cache-plug>> for more information on
  plugging in other cache stores and providers.
  
  IMPORTANT: The caching abstraction has no special handling for multi-threaded and
  multi-process environments, as such features are handled by the cache implementation.
  
negative.code: 
  To use the cache abstraction, you need to take care of two aspects:
  
  * Caching declaration: Identify the methods that need to be cached and their policies.
  * Cache configuration: The backing cache where the data is stored and from which it is read.
  
  
  