anchor.diff:  ----
   ====
   
  -Infinispan supports different transaction modes like `PESSIMISTIC` and `OPTIMISTIC`,
  +Infinispan Embedded supports different transaction modes like `PESSIMISTIC` and `OPTIMISTIC`,
   supports [acronym]`XA` recovery and provides many more configuration options;
   see the http://infinispan.org/documentation/[Infinispan User Guide]
   for more advanced configuration options.
  
positive.code: 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;
  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,
  
negative.code: 
  Referential integrity::
  While we can use relations based on foreign keys, Infinispan has no notion of referential integrity.
  Hibernate is able to maintain the integrity as it won't "forget" stale references,
  but it is possible to interrupt Hibernate OGM
  during such maintenance and then introduce breaks of integrity.
  
  When integrity could be broken::
  Using transactions, that are enabled by default, we can reduce the risk.
  In contrast, without transactions,
  when the unit of work involves several operations we might risk to have a partial writes
  (updates, deletes, inserts); some operation would be flushed to data store, other not.
  For instance let's imagine you create a new entity, remove an old one and update an association
  from the old to the new one in a single interaction,
  this would correspond to three different remote invocations: an Entity insert, an Entity delete
  and an Association update.
  If there were network problems during the third invocation,
  we could have a partial write in which only the first and the second operations
  would be actually stored on the remote storage and this could lead to a breaking referential
  integrity of the association. Because, like we said, Infinispan has no acquaintance
  of referential integrity constraints.
  
  How to detect broken integrity::
  Unfortunately, at the moment the only way to detect a referential integrity error is to
  inspect the logs for error messages or periodically monitor the associations cache and join column values.
  Our advice is to keep the default transactional configuration and rely on it.
  
  A key. And a Value.::
  In a key/value store the two elements _key_ and _value_ are different, separate objects.
  