anchor.diff:  
   
   This option comes in handy when an entire cache region needs to be cleared out. Rather
  -then evicting each entry (which would take a long time, since it is inefficient), all the
  +than evicting each entry (which would take a long time, since it is inefficient), all the
   entries are removed in one operation, as the preceding example shows. Note that the framework ignores
   any key specified in this scenario as it does not apply (the entire cache is evicted, not
   only one entry).
  
positive.code: to the method outcome.
  
  Note that `void` methods can be used with `@CacheEvict` - as the
  methods act as a trigger, the return values are ignored (as they do nt interact with the
  cache). This is not the case with `@Cacheable` which adds or updates data into the cache
  and, thus, requires a result.
  
  
negative.code: Sometimes, when switching environments or doing testing, you might have cache
  declarations without having an actual backing cache configured. As this is an invalid
  configuration, an exception is thrown at runtime, since the caching infrastructure
  is unable to find a suitable store. In situations like this, rather than removing the
  cache declarations (which can prove tedious), you can wire in a simple dummy cache that
  performs no caching -- that is, it forces the cached methods to be executed every time.
  The following example shows how to do so:
  