As can be seen in the article history I recently fall in love with Vert.x — an event-driven framework for JVM. So far there are two Vert.x related posts on this blog:
This post will be a summary of Vert.x best practices.
This is the primary and the most important rule for working with asynchronous frameworks. All Vert.x APIs are non blocking and will not block the event loop. But the issue will occur if the Event Bus will be blocked in the code. As blocking operations cannot be called directly the blocking operations need to be called within
executeBlocking method that specifies the blocking code that needs to be executed and the result handler that will be called asynchronously when the blocking operation has been completed. …
In one of the previous posts Vert.x — an event-driven application framework has been introduced. The basic features has been described as were as framework advantages and architecture. In this post, a simple Vert.x application development process will be described.
There are only two requirements: Java 8 (Vert.x requires Java 8) and a build tool of your choice. In this article Apache Maven will be used. You may also use Maven archetype to generate the project structure with all dependencies.
A standard Maven directory structure will be required:
│ ├── main
│ │ ├── java
│ │ └── resources
│ └── test
Few weeks ago I’ve discovered Vert.x — an event-driven polyglot application framework that runs on the Java Virtual Machine. I’ve already built two microservices on top of Vert.x. In this post, I’ll illustrate why I loved it.