anchor.diff:  Same as OneLaneMcDrive, but now with two lanes. There are still few customers arriving concurrently. Each of the lane
   is either free or there is maximum one customer in the lane. We have at each time between 0 and 2 customers concurrently.
   
  -* Parallelism in a execution sense: We can handle two customers at the same time
  -* Parallelism in a logical sense: like OneLaneMcDrive
  +* Parallelism in a sense of _same_ things in parallel: We can handle two customers at the same time
  +* Parallelism in a sense of _different_ things in parallel: like OneLaneMcDrive
   
   There is also no need for backpressure, since the customers arrive "slow " and the McDrive can handle them in time.
   
  
positive.code: Same as OneLaneMcDrive, but now with more customers arriving. The McDrive can't handle all of them "just in time",
  so a wait line (queue) builds up. The longer the example runs, the longer the wait line becomes.
  
  We need some kind of backpressure: we choose buffering (queueing) and get a "jam".
  
  === InfiniteLaneMcDrive
  
  
negative.code: Think of a McDrive with one lane and very few customers arriving. The one lane is either free or there is one customer.
  Each customer orders always the same three "things", which you can prepare with 3 workers in the background "in parallel".
  
  * Parallelism in a sense of _different_ things in parallel: We can do three things in parallel for one customer
  * Based on the http://reactivex.io/documentation/operators/flatmap.html[flatmap] operator (Note: @Beta annotated in RxJava 1.0.14)
  
  In this example there is no need for backpressure, since the customers arrive "slow " and the McDrive can handle them in time.
  