anchor.diff:  You need to disable native encoding for all the output individually in the case of branching. Otherwise, native encoding will still be applied for those you don't disable.
   
   When conversion is done by Spring Cloud Stream, by default, it will use `application/json` as the content type and use an appropriate json message converter.
  -You can use custom message converters by using the following property.
  +You can use custom message converters by using the following property and a corresponding `MessageConverter` bean.
   ```
   spring.cloud.stream.bindings.process-out-0.contentType
   ```
  
positive.code: }
  ```
  
  This is a rudimentary implementation, however, you have access to the key and value of the record, the topic name and the total number of partitions.
  Therefore, you can implement complex partiioning strategies if need be.
  
  You also need to provide this bean name along with the application configuration.
  
negative.code: 
  Spring Cloud Stream will ensure that the messages from both the incoming and outgoing topics are automatically bound as
  KStream objects. As a developer, you can exclusively focus on the business aspects of the code, i.e. writing the logic
  required in the processor. Setting up Kafka Streams specific configuration required by the Kafka Streams infrastructure
  is automatically handled by the framework.
  
  The two examples we saw above have a single `KStream` input binding. In both cases, the bindings received the records from a single topic.
  