anchor.diff:  
   ==== Kafka binder properties
   
  -spring.cloud.stream.binder.kafka.brokers::
  +spring.cloud.stream.kafka.binder.brokers::
     A list of brokers that the Kafka binder will connect to. Default `localhost`.
  -spring.cloud.stream.binder.kafka.defaultBrokerPort::
  +spring.cloud.stream.kafka.binder.defaultBrokerPort::
     The list of brokers allows to specify hosts with or without port information, i.e. `host1,host2:port2`. This configuration sets the default port when no port is configured in the broker list. Default `9092`.
  -spring.cloud.stream.binder.kafka.zkNodes::
  +spring.cloud.stream.kafka.binder.zkNodes::
     A list of Zookeeper nodes for the Kafka binder to connect to. Default `localhost`.
  -spring.cloud.stream.binder.kafka.defaultZkPort::
  +spring.cloud.stream.kafka.binder.defaultZkPort::
     The list of Zookeeper nodes allows to specify hosts with or without port information, i.e. `host1,host2:port2`. This configuration sets the default port when no port is configured in the node list. Default `2181`.
  -spring.cloud.stream.binder.kafka.headers::
  +spring.cloud.stream.kafka.binder.headers::
     The list of custom that will be transported by the binder. Default empty.
  -spring.cloud.stream.binder.kafka.offsetUpdateTimeWindow::
  +spring.cloud.stream.kafka.binder.offsetUpdateTimeWindow::
     The frequency in milliseconds with which offsets are saved. Ignored if `0`. Default `10000`.
  -spring.cloud.stream.binder.kafka.offsetUpdateCount::
  +spring.cloud.stream.kafka.binder.offsetUpdateCount::
     The frequency in number of updates, which which consumed offsets are persisted. Ignored if `0`. Default `0`. Mutually exclusive with `offsetUpdateTimeWindow`.
  -spring.cloud.stream.binder.kafka.requiredAcks::
  +spring.cloud.stream.kafka.binder.requiredAcks::
     The number of required acks on the broker.
   
   ==== Kafka Consumer Properties
   
   The following properties are available for Kafka consumers only and
  -must be prefixed with `spring.cloud.stream.bindings.<channelName>.`
  +must be prefixed with `spring.cloud.stream.kafka.bindings.<channelName>.consumer` .
   
   autoCommitOffset::
     True to autocommit offsets when a message has been processed. If set to false, an `Acknowledgment` header will be available in the message headers for late acknowledgment. Default `true`.
  
positive.code: 
  In addition to that, it also supports the following properties:
  
  spring.cloud.stream.binder.rabbit.addresses::
    A comma-separated list of RabbitMQ server addresses (used only for clustering and in conjunction with `nodes`). Default empty.
  spring.cloud.stream.binder.rabbit.adminAddresses. Default empty.
    A comma-separated list of RabbitMQ management plugin URLs - only used when nodes contains more than one entry. Entries in this list must correspond to the corresponding entry in addresses. Default empty.
  spring.cloud.stream.binder.rabbit.nodes::
    A comma-separated list of RabbitMQ node names; when more than one entry, used to locate the server address where a queue is located. Entries in this list must correspond to the corresponding entry in addresses. Default empty.
  spring.cloud.stream.binder.rabbit.username::
    The user name. Default `null`.
  spring.cloud.stream.binder.rabbit.password::
    The password. Default `null`.
  spring.cloud.stream.binder.rabbit.vhost::
    The virtual host. Default `null`.
  spring.cloud.stream.binder.rabbit.useSSL::
    True if Rabbit MQ should use SSL.
  spring.cloud.stream.binder.rabbit.sslPropertiesLocation::
    The location of the SSL properties file, when certificate exchange is used.
  spring.cloud.stream.binder.rabbit.compressionLevel::
    Compression level for compressed bindings. Defaults to `1` (BEST_LEVEL). See `java.util.zip.Deflater`.
  
  ==== Rabbit MQ Consumer Properties
  
  The following properties are available for Rabbit consumers only and
  must be prefixed with `spring.cloud.stream.bindings.<channelName>.`
  
  acknowledgeMode::
    The acknowledge mode. Default `AUTO`.
  
negative.code: }
  ----
  
  NOTE: Content type headers can be set by external applications in the case of Rabbit MQ, and they are supported as part of an extended internal protocol by Spring Cloud Stream for any type of transport (even the ones that do not support headers normally, like Kafka).
  
  === Binder SPI
  
  