anchor.diff:  
   NOTE: In previous versions of Spring Cloud Stream you could specify the implementation of `org.springframework.cloud.stream.binder.PartitionKeyExtractorStrategy` as `spring.cloud.stream.bindings.output.producer.partitionKeyExtractorClass` property. Since version 2.0 this property is deprecated and support for it will be removed in a future version.
   
  -Once the message key is calculated, the partition selection process will determine the target partition as a value between `0` and `partitionCount - 1`.
  +Ones the message key is calculated, the partition selection process will determine the target partition as a value between `0` and `partitionCount - 1`.
   The default calculation, applicable in most scenarios, is based on the formula `key.hashCode() % partitionCount`.
   This can be customized on the binding, either by setting a SpEL expression to be evaluated against the 'key' (via the `partitionSelectorExpression` property) or by configuring an implementation of `org.springframework.cloud.stream.binder.PartitionSelectorStrategy` as a bean (i.e., @Bean). And similarly to the `PartitionKeyExtractorStrategy` you can further filter it using `spring.cloud.stream.bindings.output.producer.partitionSelectorName` property in the event there are more then one bean of this type is available in the Application Context.
   
  
positive.code: * `BinderAwareRouterBeanPostProcessor` - while the component exists it is no longer a Bean Post Processor and will be renamed in the future.
  * `BinderProperties.setEnvironment(Properties environment)` in favor of `BinderProperties.setEnvironment(Map<String, Object> environment)`.
  	
  
  == Introducing Spring Cloud Stream
  Spring Cloud Stream is a framework for building message-driven microservice applications.
  
negative.code: In the example above, we are creating an application that has an input and an output channel, bound through the `Processor` interface.
  The bound interface is injected into the test so we can have access to both channels.
  We are sending a message on the input channel and we are using the `MessageCollector` provided by Spring Cloud Stream's test support to capture the message has been sent to the output channel as a result.
  Ones we have received the message, we can validate that the component functions correctly.
  
  === Disabling the test binder autoconfiguration
  
  