Looking to the future...

By Alessio Soldano | October 8, 2019

If you look at the download page, you might notice that so far 2019 has been a year rich of RESTEasy releases. We've made 11 new versions available to the community, starting a new major (4.0) and six new minor (3.7, 3.8, 3.9, 4.1, 4.2, 4.3) streams . This was partially because we're trying to avoid including features in micro version releases and we're carefully ensuring that anything that is backported to RESTEasy 3 is fully backward compatible, so that it can be consumed by WildFly. The other reason for the high number of minor releases… is basically that we've got a lot of good quality contributions from the community! Thanks!

As the releases have been somehow unpredictable, I wanted to write down and share a development roadmap, but these days that's quite a difficult task, especially considering that now RESTEasy is looking at both JakartaEE and Microprofile evolution (which is far from being set in stone ;-)), while both WildFly and Quarkus are feeding RESTEasy's requirements tracking list and begging for frequent releases ;-) So I think I'll start with providing some highlights on the areas where the core team is currently willing to focus in the next 12-18 months; clearly I expect the community to influence the actual future of the project.

JakartaEE

JakartaEE 8 is here and 9 is being planned these days. When it comes to the Jakarta RESTful Web Services, the spec group is already actively working on version 2.2 and thinking about the following ones. RESTEasy will definitely implement the latest versions on master (we actually have a prototype of the new SE boostrap API ready since months); the backport to 3.x stream will have to be coordinated with WildFly efforts around JakartaEE upgrades.

MicroProfile

RESTEasy is implementing MicroProfile REST Client 1.3 and will be updating to new versions should they be produced by the spec working group. Besides that, we have plans for improving the integration of some of the other MicroProfile technologies in RESTEasy (OpenAPI, OpenTracing, Config). The efforts are possibly going to be on both master and 3.x: as Brian recently announced, MicroProfile is going to be a significant focus for the next couple of WildFly releases.

Quarkus integration improvements

I foresee multiple contributions and request for enhancements coming from the Quarkus land in the very next future. A few examples of possible improvements would be the support for non-blocking IO on server side and possibly an abstraction layer for the access to annotations, to avoid RESTEasy performing a lot of annotation scanning at runtime.

WildFly integration improvements

In addition to the JakartaEE and MicroProfile efforts mentioned above, we still have a few new features that were planned for previous WildFly releases but haven't been completed yet. I'm thinking about exposing statistics for RESTEasy resources in the WildFly management model and possibly adding a new module for WADL support. 

That's it for now, I promise I will try to update you on the plans in the future!

Stay tuned … and keep on contributing!