anchor.diff:  logs the generated schemas at `INFO` level in the logging category
   `org.hibernate.ogm.datastore.infinispanremote.impl.protobuf.SchemaDefinitions`.
   
  +[[storage-principles-of-infinispan-dataprovider]]
  +
   ==== Storage Principles of the Infinispan Remote dataprovider
   
   This is actually very simple.
  
positive.code: Hibernate is able to maintain the integrity as it won't "forget" stale references, but since
  the storage doesn't support transactions either it is possible to interrupt Hibernate OGM
  during such maintenance and introduce breaks of integrity.
  
  A key. And a Value.::
  In a key/value store the two elements _key_ and _value_ are different, separate objects.
  
negative.code: is similar to having Hibernate connect to traditional database: the data is stored
  on the _Infinispan Server_ nodes, and Hibernate OGM uses a client with a pool of
  TCP connections to talk to the server.
  But the Hot Rod client is not transactional, see the limitation described here:
  (<<storage-principles-of-infinispan-dataprovider>>).
  
  Another important difference, is that when connecting to _Infinispan Server_ via
  _Hot Rod_ the data is encoded using _Google Protobuf_, which requires a schema.
  