anchor.diff:  
   ```
   
  -
   === State Cleanup
   
   By default, the `Kafkastreams.cleanup()` method is called when the binding is stopped.
  
positive.code: 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 `trasform` or `process` method API calls to get access to the processor API.
  
  Here is a look at how one may combine both the DSL and the processor API in a Spring Cloud Stream application using the `process` API.
  
  
negative.code: 
  After that, you must set all the binding level properties on these new binding names.
  
  Please keep in mind that with the functional programming model described above, adhering to the default binding names make sense in most situations.
  The only reason you may still want to do this overriding is when you have larger number of configuration properties and you want to map the bindings to something more domain friendly.
  
  ==== Setting up bootstrap server configuration
  