Hi all,
It's been a long while but here we are!
We are very pleased to announce the release of Vert.x 3.3.0! This release is huge with lots of new features, improvements and bug fixes (obviously) that we won’t details all the new features here (some are below).
- full release notes are available:
https://github.com/vert-x3/wiki/wiki/3.3.0---Release-Notes
- breaking changes:
https://github.com/vert-x3/wiki/wiki/3.3.0-Breaking-Changes
The artifacts have been deployed to Maven Central and you can get the distribution on Bintray also available from SDKMan and Homebrew.
The event bus client using the SockJS bridge is available from NPM, Bower and as a WebJar:
-
https://www.npmjs.com/package/vertx3-eventbus-client
-
https://github.com/vert-x3/vertx-bus-bower
-
http://www.webjars.org/
Docker images are also available on the Docker Hub.
The examples have also been upgraded to 3.3.0 :
https://github.com/vert-x3/vertx-examples/
Let’s highlight some of the major features shipped with this release.
Vertx 3.3.0 is the first version to support HTTP2 (client and server). You can now configure HTTP servers and clients to use HTTP2. Proxy support for TCP and HTTP clients has also been added.
This version also introduces a new bridge with Apache Camel. Integrating Vert.x applications with legacy systems (using EIP) has never been so easy.
Several new components have been developed to implement microservice-based applications. First, a pluggable service discovery is now available. An implementation of the circuit breaker pattern has also been provided.
AMQP support has been also integrated via a bridge to send and receive messages from AMQP. A client is also shipped to interact directly with an AMQP broker or router.
New metrics are introduced to ease the monitoring of running applications. For instance, it’s now possible to monitor the thread usage in the worker thread pool and in the JDBC connection pools.
With this version, you can configure the TCP aspects of the event bus to, for instance, use SSL. Take also note of a new a bridge between the event bus of Vert.x 2 and Vert.x 3.
Most of the delivered components are now deployable in OSGi environments. So you can easily integrate Vert.x in Apache Karaf, Service Mix, or Apache Sling.
Vert.x Unit usability has been greatly improved. It is now possible to write test using Hamcrest, AssertJ, Rest Assured, or any assertion libraries you want.
Many thanks to all the committers and community whose contributions made this possible, especially to Alex Lehman, Paul Bakker, Robbie Gemmel, Claus Ibsen, Michael Kremer, and many many other !
Last but not least I want to thank Clement and Paulo for the impressive contributions they have made to Vert.x - both joined the Vert.x core team a year ago and their presence has made a significant difference!!!
Just a word about the future. As we did last, year, a poll will be organized in the next few weeks to collect ideas and prioritize the Vert.x 3.4 and beyond roadmap. Stay tuned, we love hearing about your ideas and issues.
Happy coding !
Julien