Use of verticles with Vert.x is entirely optional, but if you use them they provide an actor-like deployment and concurrency model, out of the box.
Vert.x does not provide a strict actor implementation, but there are significant similarities.
You can think of verticle instances as a bit like actors in the Actor Model. A typical verticle-based Vert.x application will be composed of many verticle instances in each Vert.x instance.
The verticles communicate with each other by sending messages over the io..
| Modifier and Type | Method and Description |
|---|---|
| public Vertx | Returns: A reference to the Vert.x instanceGet a reference to the Vert.x instance that deployed this verticle |
| public void | |
| public void | |
| public void |
| getVertx | back to summary |
|---|---|
| public Vertx getVertx() Get a reference to the Vert.x instance that deployed this verticle
| |
| init | back to summary |
|---|---|
| public void init(Vertx vertx, Context context) Initialise the verticle with the Vert.x instance and the context. This method is called by Vert.x when the instance is deployed. You do not call it yourself. | |
| start | back to summary |
|---|---|
| public void start(Promise<Void> startPromise) throws Exception Start the verticle instance. Vert.x calls this method when deploying the instance. You do not call it yourself.
A promise is passed into the method, and when deployment is complete the verticle should either call
| |
| stop | back to summary |
|---|---|
| public void stop(Promise<Void> stopPromise) throws Exception Stop the verticle instance. Vert.x calls this method when un-deploying the instance. You do not call it yourself.
A promise is passed into the method, and when un-deployment is complete the verticle should either call
| |