anchor.diff:  
   In your browser, navigate to http://localhost:8080/hello/Quarkus/object. You should see:
   
  -[source]
  +[source, text]
   ----
   {"Hello":"Quarkus"}
   ----
   
   Then, navigate to http://localhost:8080/hello/Quarkus/array:
   
  -[source]
  +[source, text]
   ----
   ["Hello","Quarkus"]
   ----
   
   Needless to say, this works equally well when the JSON result is wrapped in a `CompletionStage` or a `Publisher`.
   
  -== Using the Reactive clients
  -
  -TODO: talk about the existing clients, in particular the Axle shims
  -
  -=== Web Client
  -
  -TODO
  -
  -
  -//////
  -It comes from another Vert.x shim, _Axle_, similar to the _Rxified_ one, but that uses the `CompletionStage` type for single results and `Publisher` for streams.
  -
  -TIP: You may inject any of the 3 flavors of `Vertx` or `EventBus` in your {project-name} application beans: `core`, `Axle`, `RxJava`.
  -They are just shims and rely on a single Vert.x instance.
  -
  -You will pick one or the other depending on your use cases.
  -
  -- `core`: for advanced usage or if you have existing Vert.x code you want to reuse in your {project-name} application
  -- `Axle`: works well with {project-name} and Microprofile APIs (`CompletionStage` for single results and `Publisher` for streams)
  -- `RxJava`: when you need support for a wide range of data transformation operators on your streams
  -//////
  +== Using the event bus
  +
  +The event bus is the connecting tissue of Vert.x application.
  +{project-name} integrates it so different beans can interact asynchronous messages.
  +This part is covered in the link:async-message-passing.html[Async Message Passing documentation].
  +
  +//== Using the Reactive clients
  +//
  +//TODO: talk about the existing clients, in particular the Axle shims
  +//
  +//=== Web Client
  +//
  +//TODO
  +
  
positive.code: </dependency>
  ----
  
  === Reactive web resources
  
  {project-name} web resources support asynchronous processing and streaming results over https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events[server-sent events].
  
  ==== Asynchronous processing
  
  Most programming guides start easy with a greeting service and this one makes no exception.
  
  
negative.code: ...
  ----
  
  === Using JSON results
  
  Vert.x API heavily relies on JSON, namely the `io.vertx.core.json.JsonObject` and `io.vertx.core.json.JsonArray` types.
  They are both supported as {project-name} web resource return types.
  