anchor.diff:  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 then removing the
  +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:
  
positive.code: that are affected by the action, allows a custom cache and key resolution or a
  condition to be specified, and features an extra parameter
  (`allEntries`) that indicates whether a cache-wide eviction needs to be performed
  rather then just an entry eviction (based on the key). The following example evicts
  all entries from the `books` cache:
  
  [source,java,indent=0]
  
negative.code: 
  The terms, "`buffer`" and "`cache,`" tend to be used interchangeably. Note, however,
  that they represent different things. Traditionally, a buffer is used as an intermediate
  temporary store for data between a fast and a slow entity. As one party would have to wait
  for the other (which affects performance), the buffer alleviates this by allowing entire
  blocks of data to move at once rather than in small chunks. The data is written and read
  only once from the buffer. Furthermore, the buffers are visible to at least one party
  that is aware of it.
  
  