Vert.x provides a large ecosystem of reactive APIs that are integrated into Quarkus. More specifically, Quarkus uses Vert.x as the reactive engine by providing a single dependency to your applications:
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-vertx</artifactId>
</dependency>
This allows you to access a managed Vert.x instance with simple code injection:
@Inject io.vertx.core.Vertx vertx;
The Vertx object is the control center of a Vert.x application. It's your pass to Vert.x land and allows you to create an asynchronous and non-blocking client and servers, get a reference to the Event Bus, and many other things.
When using Vert.x API in Quarkus, however, there's no Vertx object for you to access. As a matter of fact, Quarkus provides three different Vert.x APIs:
- io.vertx.core...