anchor.diff:  We always recommend using transactional caches, at least unless you are confident that data consistency is not important for your use case.
   ====
   
  +==== Remote Query Capability
  +
  +Hibernate OGM backend is able to run the queries it needs to materialize relations.
  +From version __5.4.0.Alpha2__ the dialect is capable to translate JPQL or Criteria queries to the Infinispan remote queries.
  +But there are still some limitations:
  +
  +* We don't support queries on polymorphic entities using TABLE_PER_CLASS inheritance strategy
  +* Selecting from associations is not yet implemented
  +* Query on Byte filed is not currently supported
  +
   ==== Known Limitations & Future improvements
   
   The Infinispan Remote dataprovider has some known limitations, some of which are
  
positive.code: Transaction Support::
  We're eagerly waiting for Infinispan to support transactions over Hot Rod, as it
  already provides this feature in Embedded Mode.
  
  Queries::
  At this point the Hibernate OGM backend is able to run the queries it needs to materialize
  relations, but does not yet translate JPQL queries nor Criteria queries to the
  Infinispan remote queries.
  
  Indexing::
  Infinispan supports Hibernate Search annotations directly embedded within its protobuf
  
negative.code: to a "cache name". In the above example, when having an `Hypothesis` entity this will
  write to a Cache named `Hypothesis`.
  
  The benefit is that you can tune, or query, each cache (each "table") independently; for example you could
  configure the caches for the most important data to have a synchronous CacheStore which replicates
  data to a relational database, and have less important entries use an asynchronous CacheStore,
  or none at all, to favour performance over redundancy.
  
  ==== Caches creation and Configuration
  
  