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: </dependency>
  ----
  
  ====== Multiple binders on the classpath
  
  When multiple binders are present on the classpath, the application must indicate what binder has to be used for the channel. Each binder configuration contains a `META-INF/spring.binders`, which is in fact a property file:
  
  [source]
  ----
  
negative.code: [partintro]
  --
  This section goes into more detail about how you can work with Spring Cloud Stream. It covers topics
  such as creating and running stream applications.
  --
  
  === Introducing Spring Cloud Stream
  
  The Spring Cloud Stream project allows a user to develop and run messaging microservices using Spring Integration.
  Just add `@EnableBinding` and run your app as a Spring Boot app (single application context).
  Spring Cloud Stream applications connect to the physical broker through bindings, which link Spring Integration
  channels to physical broker destinations, for either input (consumer bindings) or output (producer bindings).
  The creation of the bindings, and therefore their broker-specific implementation is handled by a binder, which is
  another important abstraction of Spring Cloud Stream. Binders abstract out the broker-specific implementation details.
  In order to connect to a specific type of broker (e.g. Rabbit or Kafka) you just need to have the relevant binder
  implementation on the classpath.
  
  Here's a sample source app (output channel only):
  
  [source,java]
  ----
  @SpringBootApplication
  public class StreamApplication {
  
    public static void main(String[] args) {
      SpringApplication.run(StreamApplication.class, args);
    }
  }
  
  @EnableBinding(Source.class)
  public class TimerSource {
  
  