anchor.diff:          System.out.println("Cannot read the file: " + ar.cause().getMessage());
       }
   });
  +
  +// Mutiny Vert.x:
  +vertx.fileSystem().readFile("lorem-ipsum.txt")
  +    .onItem().apply(buffer -> buffer.toString("UTF-8"))
  +    .subscribe(
  +            content -> System.out.println("Content: " + content),
  +            err -> System.out.println("Cannot read the file: " + err.getMessage())
  +    );
   
   // Rx Java 2 Vert.x
   vertx.fileSystem().rxReadFile("lorem-ipsum.txt")
  
positive.code: Eclipse https://vertx.io[Vert.x] is a toolkit for building reactive applications.
  It is designed to be lightweight and embeddable.
  Vert.x defines a reactive execution model and provides a large ecosystem.
  Quarkus integrates Vert.x to implement different reactive features, such as asynchronous message passing, and non-blocking HTTP client.
  Basically, Quarkus uses Vert.x as its reactive engine.
  While lots of reactive features from Quarkus don't _show_ Vert.x, it's used underneath.
  But you can also access the managed Vert.x instance and benefit from the Vert.x ecosystem.
  
  == Installing
  
  
negative.code: ----
  
  If you are familiar with Vert.x, you know that Vert.x provides different API models.
  For instance _bare_ Vert.x uses callbacks, the Mutiny variants uses `Uni` and `Multi`, the RX Java 2 version uses `Single`, `Maybe`, `Completable`, `Observable` and `Flowable`...
  
  Quarkus provides 4 Vert.x APIs:
  
  [options="header"]
  |===
  