anchor.diff:  ****
   
   You may wonder why synchronization is not required. Indeed we write in the map and read from it without any
  -synchronization constructs. Here is one of the main feature of Vert.x: all this code is going to be executed by
  +synchronization constructs. Here is one of the main features of Vert.x: all this code is going to be executed by
   the **same** event loop, so it's always accessed by the **same** thread, never concurrently.
   
   TIP: The `Map<String, JsonObject>` could be replaced by a simple `JsonObject` as they behave as a `Map<String, Object>`.
  
positive.code:     })
  ----
  
  First, it retrieves the message body (1). It's a JSON object, and stores it in the `quotes` map (2).
  ****
  
  #### Task - Implementing a Handler to handle HTTP requests
  
  Now that you have the `quotes`, let's use it to handle HTTP request. The code already creates the HTTP server and
  provides the stream of HTTP requests. The stream emits an item for every HTTP request received by the server. So, you
   need to handle the request and write the response.
  
  
negative.code: 
  ### Verticle
  
  As you may have noticed, the code is structured in 3 `verticles`, but what are these? Verticles are a way to structure
   Vert.x application code. It's not mandatory, but it is quite convenient. A verticle is a chunk of code that is
   deployed on top of a Vert.x instance. A verticle has access to the instance of `vertx` on which it's deployed and
   can deploy other verticles.
  
  Let's open the `GeneratorConfigVerticle` class, and look at the `start` method:
  