anchor.diff:  One could sum this up to:
   
   Rx is created mainly for "clients" (client applications like apps, desktop gui applications, ...) where
  -you have typically one thread from the GUI and you would like to - on e.g. a form submit - "spin off" several background tasks (in parallel),
  +you have typically one thread from the GUI and you would like to on e.g. a form submit "spin off" several background tasks (in parallel),
   combine those asynchronously returning results to one result which you display in the GUI.
   
   It's not primarly made for "servers", e.g. to handle concurrent HTTP requests in a webserver. But you can use it to do implement "servers", if you know "how".
  
positive.code: == Handling Observables parallel (in a logical sense and in a execution sense)
  
  Probably you also had a difficult start concerning RxJava and threading like http://www.grahamlea.com/2014/07/rxjava-threading-examples.
  
  I had.
  
  
negative.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
  
  