anchor.diff:  
   ====== BiConsumer in Kafka Streams Binder
   
  -If there are two inputs, but no outputs, in that case we can use `java.util.funcion.BiConsumer` as shown below.
  +If there are two inputs, but no outputs, in that case we can use `java.util.function.BiConsumer` as shown below.
   
   [source]
   ----
  
positive.code: 
  === Mixing high level DSL and low level Processor API
  
  Kafka Streams provides two variants of API's.
  It has a higher level DSL like API where you can chain various operations that maybe familiar to a lot of functional programmers.
  Kafka Streams also gives access to a low level Processor API.
  The processor API, although very powerful and gives the ability to control things in a much lower level, is imperative in nature.
  Kafk Streams binder for Spring Cloud Stream, allows you to use either the high level DSL or mixing both the DSL and the processor API.
  Mixing both of these variants give you a lot of options to control various use cases in an application.
  Applications can use the `transform` or `process` method API calls to get access to the processor API.
  
  
negative.code: 
  If Serde inference fails, and no binding level Serdes are provided, then the binder falls back to the `JsonSerde`, but look at the default Serdes for a match.
  
  Default serdes are configured in the same way as above where it is described under deserialization.
  
  `spring.cloud.stream.kafka.streams.binder.configuration.default.key.serde`
  `spring.cloud.stream.kafka.streams.binder.configuration.default.value.serde`
  