Hello Reactor community,
On behalf of the Reactor team and its heroic new contributors, I am delighted to announce that Reactor Dysprosium can now be found on your preferred Maven repositories, like this one.
It is the fourth release train since Reactor Core 3.x and it includes
Reactor Core 3.3,
Reactor Netty 0.9 and a newcomer,
Reactor Pool 0.1. Check out the major change logs and release notes:
- reactor-core 3.3.0.RELEASE
- reactor-netty 0.9.0.RELEASE
- reactor-pool 0.1.0.RELEASE
Reactor Dysprosium modules still require JDK 8 or higher. They come with many performance improvements and we even have identified more areas to focus on the next patches and major releases. Please join me in giving a warm welcome to a new module to the family, Reactor Pool. It is the generic embeddable reactive object pool you were waiting for. It is used by Reactor Netty and we plan to build more features on top of it. As with Reactor Netty, we haven’t qualified a major “1.x” release as we expect tweaks before considering it API stable.
Be sure to try out the new Metrics support and documentation that have been introduced to Reactor Netty.
Alongside the release train we also introduce
Blockhound, check its first 1.0.0.RELEASE. It’s a small util aimed at finding out if you are throwing a blocking wrench in your nice non blocking flow, whether it’s Reactor or any other non blocking library.
Finally, we have ended support for Bismuth with the release of
Dysprosium. We encourage our users to update to the latest and greatest. We are still supporting
Californium release train, which matches Spring Boot 2.1.x and Spring Framework 5.1.x.
See you at SpringOne in Austin for those of you coming by.