anchor.diff:  
   NOTE: we recommend only using the Redis Binder for development
   
  -The Redis Binder creates a LIST for each consumer group. A consumer binding will trigger BRPOP operations on that LIST. A producer binding will consult a ZSET to determine what groups currently have active consumers, and then for each message being sent, an LPUSH operation will occur on each of those LISTs.
  +The Redis Binder creates a `LIST` (which performs the role of a queue) for each consumer group. A consumer binding will
  +trigger `BRPOP` operations on its group's `LIST`. A producer binding will consult a `ZSET` to determine what groups
  +currently have active consumers, and then for each message being sent, an `LPUSH` operation will be executed on each of
  +those group's `LISTs`.
  
positive.code: org.springframework.cloud.stream.binder.rabbit.config.RabbitServiceAutoConfiguration
  ----
  
  Similar files exist for the other binder implementations (i.e. Kafka and Redis), and it is expected that custom binder implementations will provide them, too. The key represents an identifying name for the binder implementation, whereas the value is a comma-separated list of configuration classes that contain one and only one bean definition of the type `org.springframework.cloud.stream.binder.Binder`.
  
  Selecting the binder can be done globally by either using the `spring.cloud.stream.defaultBinder` property, e.g. `spring.cloud.stream.defaultBinder=redis`, or by individually configuring them on each channel.
  
  For instance, a processor module that reads from Rabbit and writes to Redis can specify the following configuration: `spring.cloud.stream.bindings.input.binder=rabbit`,`spring.cloud.stream.bindings.output.binder=redis`.
  
  ====== Connecting to multiple systems
  
  By default, binders share the Spring Boot autoconfiguration of the application module and create one instance of each binder found on the classpath. In scenarios where a module should connect to more than one broker of the same type, Spring Cloud Stream allows you to specify multiple binder configurations, with different environment settings. Please note that turning on explicit binder configuration will disable the default binder configuration process altogether, so all the binders in use must be included in the configuration.
  
  For example, this is the typical configuration for a processor that connects to two rabbit instances:
  
  [source,yml]
  ----
  
negative.code: </dependency>
  ----
  
  ====== Multiple Binders on the Classpath
  
  When multiple binders are present on the classpath, the application must indicate which binder is to be used for each
  channel binding. Each binder configuration contains a `META-INF/spring.binders`, which is a simple properties file:
  
  [source]
  ----
  