anchor.diff:  ----
   
   ==== Example 2 - limiting access to service by contract agreements
  -> Imagine that you provide paid language translation service via HTTP. Each user has unique agreement which differs from each other.
  -Details of each agreement is stored in relational database, and takes significant time to fetch(for example 100ms). 
  -The example above will not work fine in this case, because time to create/fetch configuration of bucket from database
  +> Imagine that you provide paid language translation service via HTTP. Each user has a unique agreement that differs from the other.
  +Details of each agreement are stored in a relational database and take significant time to fetch(for example 100ms).
  +The example above will not work fine in this case, because time to create/fetch the configuration of the bucket from the database
   will be 100 times slower than limit-checking itself.
  -Bucket4j solves this problem via lazy configuration suppliers which are called if and only if bucket was not yet stored in grid,
  -thus it is possible to implement solution  that will read agreement from database once per each user.
  +Bucket4j solves this problem via lazy configuration suppliers which are called if and only if the bucket was not yet stored in the grid,
  +thus it is possible to implement a solution that will read the agreement from the database once per user.
   
   [source, java]
   ----
  
positive.code: * <<bucket4j-infinispan, bucket4j-infinispan>>
  * <<bucket4j-coherence, bucket4j-coherence>>
  
  Also, implementation the asynchronous support for any other JCache provider outside from the list above should be easy exercise, so feel free to return back the pull request addressed to cover your favorite JCache provider.
  
  ==== Verification of compatibility with particular JCache provider is your responsibility
  IMPORTANT: Keep in mind that there are many non-certified implementations of JCache specification on the market.
  Many of them want to increase their popularity by declaring support for the JCache API,
  but often only the API is supported and the semantic of JCache is totally ignored.
  Usage Bucket4j with this kind of libraries should be completely avoided.
  
  Bucket4j is only compatible with implementations which obey the JCache specification rules(especially related to EntryProcessor execution). Oracle Coherence, Apache Ignite, Hazelcast are good examples of safe implementations of JCache.
  
  IMPORTANT: Because it is impossible to test all possible JCache providers, you need to test your provider by yourself.
  
  
negative.code: </dependency>
  ----
  
  JCache expects javax.cache.cache-api to be a provided dependency. Do not forget to add the following dependency:
  [source, xml]
  ----
  <dependency>
  