anchor.diff:  Once enabled `RoutingFunction` will be bound to input destination
   receiving all the messages and route them to other functions based on the provided instruction.
   
  +IMPORTANT: For the purposes of binding the name of the routing destination is `functionRouter-in-0`
  +(see RoutingFunction.FUNCTION_NAME and binding naming convention <<Functional binding names>>).
  +
   Instruction could be provided with individual messages as well as application properties.
   
   Here are couple of samples:
   
  -***Using message headers***
  +===== Using message headers
   [source,java]
   ----
   @SpringBootApplication
  
positive.code: This is useful, for example, when the target destination needs to be determined at runtime.
  Applications can do so in one of two ways
  
  ***BinderAwareChannelResolver***
  
  The `BinderAwareChannelResolver` is a special bean registered automatically by the framework.
  You can autowire this bean into your application and use it to resolve output destination at runtime
  
negative.code: The destinations, 'customers' and 'orders', are created in the broker (in the exchange for Rabbit or in the topic for Kafka)
  with names of 'customers' and 'orders', and the data is published to the appropriate destinations.
  
  ===== spring.cloud.stream.sendto.destination
  
  You can also delegate to the framework to dynamically resolve the output destination by specifying `spring.cloud.stream.sendto.destination` header
  set to the name of the destination to be resolved.
  