anchor.diff:  [source, JAVA]
   ----
   @Entity
  +@WriteConcern(WriteConcernType.JOURNALED)
   @AssociationStorage(AssociationStorageType.ASSOCIATION_DOCUMENT)
   @AssociationDocumentStorage(AssociationDocumentType.COLLECTION_PER_ASSOCIATION)
   public class Zoo {
  
positive.code: ----
  ====
  
  The annotations on the entity level express that all associations of the +Zoo+
  class should be stored in separate assocation documents, using a dedicated collection per association.
  This setting applies to the +animals+ and +employees+ associations.
  Only the elements of the +visitors+ association will be stored in the document of the corresponding +Zoo+ entity
  
negative.code: ===== Annotation based configuration
  
  Hibernate OGM allows to configure store-specific options via Java annotations.
  When working with the MongoDB backend, you can specify the following settings:
  
  * the write concern for entities and associations using the +@WriteConcern+ annotation
  * a strategy for storing associations using the +@AssociationStorage+ and +@AssociationDocumentStorage+ annotations
  (refer to <<ogm-mongodb-storage-prinicples>> to learn more about these options).
  
  The following shows an example:
  