anchor.diff:  [#configuration_server]
   === Server
   
  -A link:../../../../src/microservice/server.ts[Server] instance can provide multiple service endpoints
  +A link:https://github.com/restorecommerce/chassis-srv/blob/master/src/microservice/server.ts[Server] instance can provide multiple service endpoints
   and emits events related with the microservice's state.
   An endpoint is a wrapped gRPC method accessible from any gRPC clients.
   It is also possible to configure the Server with number of times a request should be
  -link:../../../..//test/microservice_test.ts[`retried and timeout configurations`].
  +link:https://github.com/restorecommerce/chassis-srv/blob/master/test/microservice_test.ts#L456[`retried and timeout configurations`].
   Service responses always include a result or an error. When a `Server` is instantiated,
   it is possible to bind one or more services to it, each of them exposing its own RPC endpoints
   with an associated transport configuration (port, protobuf interfaces, service name, etc).
  
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: [#configuration_middleware]
  === Middleware
  
  Endpoint calls may be intercepted with any number of link:https://github.com/restorecommerce/chassis-srv/blob/master/test/middleware_test.ts[custom chained middlewares].
  The request traverses the middleware before reaching the service function.
  The middleware can call the next middleware until the last middleware calls the service function.
  
  