Vert.x 3.3.0 is released!

That was a long run … but here we are. We are very pleased to an­nounce the re­lease of Vert.x 3.3.0!

This re­lease is huge with lots of new fea­tures, im­prove­ments, and ob­vi­ously bug fixes. We won’t de­tail all the new fea­tures here (some are high­lighted below), and full re­lease notes are avail­able: https://github.com/vert-​x3/wiki/wiki/3.3.0-​—Release-Notes

Break­ing changes are there: https://github.com/vert-​x3/wiki/wiki/3.3.0-​—Breaking-Changes. Be sure to read them be­fore mi­grat­ing.

The event bus client using the SockJS bridge are avail­able from NPM, Bower and as a We­b­Jar:

• https://www.npmjs.com/pack­age/vertx3-​eventbus-client
• https://github.com/vert-​x3/vertx-​bus-bower
• http://www.we­b­jars.org/

Docker im­ages are also avail­able on the Docker Hub. The Vert.x dis­tri­b­u­tion is also avail­able from SD­KMan and Home­Brew.

Let’s high­light some of the major fea­tures shipped with this re­lease.

• Vertx 3.3.0 is the first ver­sion to sup­port HTTP2 (client and server). You can now con­fig­ure HTTP servers and clients to use HTTP2. Proxy sup­port for TCP and HTTP client has also been added.
• This ver­sion shows also the in­tro­duc­tion of a bridge with Apache Camel. So, in­te­grat­ing Vert.x ap­pli­ca­tions with legacy sys­tems (using EIP) has never been so easy.
• Sev­eral new com­po­nents have been de­vel­oped to im­ple­ment microservice-​based ap­pli­ca­tions. First, a plug­gable ser­vice dis­cov­ery is now avail­able. An im­ple­men­ta­tion of the cir­cuit breaker pat­tern has also been pro­vided.
• AMQP 1.0 sup­port has been also in­te­grated thanks to a bridge to send and re­ceive mes­sages from AMQP. A client has also been shipped to in­ter­act di­rectly with an AMQP bro­ker or router.
• New met­rics has also been in­tro­duced to ease the mon­i­tor­ing of run­ning ap­pli­ca­tions. For in­stance, it’s now pos­si­ble to mon­i­tor the thread usage in the worker thread pool and in the JDBC con­nec­tion pools.
• With this ver­sion, you can con­fig­ure the TCP as­pects of the event bus for, for in­stance, use SSL. Also no­tice a bridge be­tween the event bus of Vert.x 2 and the one from Vert.x 3.
• Most of the de­liv­ered com­po­nents are now de­ploy­able in OSGi en­vi­ron­ments. So you can eas­ily in­te­grate Vert.x in Apache Karaf, Ser­vice Mix, or Apache Sling.
• Vert.x Unit us­abil­ity has been greatly im­proved. It is now pos­si­ble to write test using Ham­crest, As­sertJ, Rest As­sured, or any as­ser­tion li­braries you want.

Many thanks to all the com­mit­ters and com­mu­nity whose con­tri­bu­tions made this pos­si­ble, es­pe­cially to Alex Lehman, Paul Bakker, Rob­bie Gem­mel, Claus Ibsen, Michael Kre­mer, and many many other!

The ar­ti­facts have been de­ployed to Maven Cen­tral and you can get the dis­tri­b­u­tion on Bin­tray.

Just a word about the fu­ture. As we did last, year, a poll will be or­ga­nized in the next few weeks to col­lect ideas and pri­or­i­tize the Vert.x 3.4 and be­yond roadmap. Stay tuned, we love hear­ing about your ideas and is­sues.

Happy cod­ing !