anchor.diff:  are encoded in the value *as well*, as it is not possible to run e.g. range queries
   on attributes of keys.
   
  -No Sequences, no auto-incrementing values::
  -Infinispan does not support sequences, yet allows concurrent "compare and set" operations;
  +Sequences and auto-incrementing values::
  +Infinispan now support sequences, they are created by the dialect where a `@SequenceGenerator` annotation is present.
  +On the other hand `@TableGenerator` still use the old Hibernate OGM "compare and set" implementation;
   Hibernate OGM makes use of such CAS operations to emulate the need of sequences or auto-incrementing
   primary keys if your entity mapping uses them, however this solution might not work
   under high load: make sure to use a different strategy, such as assigning IDs explicitly,
  
positive.code: ==== 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 to the **corresponding** Infinispan remote queries
  or to execute native queries.
  But there are still some limitations:
  
  
negative.code: This doesn't affect how entities are encoded so the specified schema is expected to be compatible with the generated one.
  This can be used to defined server side indexes on caches used by JPQL and native Ickle queries.
  
  hibernate.ogm.cache.transaction.mode::
  Property is used to configure the transaction mode of Infinispan caches.
  Possible values are: `XA`, `NON_DURABLE_XA` (the default), `NON_XA` and `NONE` (the one to disable transaction).
  For more information see the chapter <<infinispan-remote-transaction>>.
  
  ==== Data encoding: Protobuf Schema
  
  Using the _Infinispan Remote_ backend your data will be encoded using Protocol Buffers,
  