anchor.diff:  Hibernate OGM uses a sophisticated configuration mechanism that obtains
   its values from various sources. Most common configuration sources are:
   
  -* hibernate.properties file
  -* persistence.xml file
  +* `hibernate.properties` file
  +* `persistence.xml` file
   * annotation configuration (entity classes)
   * programmatic configuration
   
  
positive.code: 
  === How to build support for a data store
  
  Hibernate OGM supports various data stores by abstracting them
  with `DatastoreProvider` and `GridDialect`. The supported features vary between data stores,
  and dialects do not have to implement all features. Hibernate OGM implements a TCK
  
negative.code: certain nature, how to map data. Document-oriented data stores encourage
  an entity-as-document pattern where embedded data structures could be
  stored within the document itself. Key-value data stores allow different
  approaches, e.g. storing an entity as JSON document or event storing
  individual key-value pairs that map the entity within a hash table
  data structure. Hibernate OGM allows multiple dialects per data store
  and users may choose the most appropriate one.
  