anchor.diff:  * custom middleware
   * a cache-loader based on configuration files
   * a provider-based mechanism to access different databases
  -* a base implementation for a link:./command-interface.adoc[command-interface]
  +* a base implementation for a link:https://github.com/restorecommerce/chassis-srv/blob/master/docs/modules/ROOT/pages/command-interface.adoc[command-interface]
   * periodic storage for https://kafka.apache.org/[Apache Kafka] topic offsets
   
   [#configuration]
  
positive.code: https://github.com/restorecommerce/service-config[service-config].
  Such configuration files may contain endpoint specifications
  along with their associated transports or simple access configs for backing services such as a database or even a Kafka instance.
  To remove the buffered data from being logged link:../../../../test/cfg/config.json[bufferedFields] configuration can be set.
  
  [#configuration_logging]
  === Logging
  
negative.code: Query parameter structure for all exposed operations is similar with the structure used in
  https://docs.mongodb.com/manual/tutorial/getting-started/[MongoDB] queries.
  The ArangoDB provider supports graph database creation and exposes a simple API to manage vertices and edges.
  It also provides a flexible traversal method. For more details, see link:https://github.com/restorecommerce/chassis-srv/blob/master/test/graphs_test.ts[graph tests]
  and the https://docs.arangodb.com/3.3/HTTP/Gharial/[ArangoDB graphs documentation].
  Database providers can be used as a database abstraction by any service that owns a set of resources.
  Furthermore, services can later expose their database operations via gRPC.
  