Mutiny 2.0.0 is now available!

[jponge]

Mutiny 2.0.0 Announcement

We are pleased to announce the availability of Mutiny 2.0.0, an intuitive event-driven reactive programming library for Java.

While Mutiny 2 is a major release with source and binary incompatible changes to the Mutiny 0.x and 1.x series, the upgrade is transparent for most code bases that use Mutiny in applications (e.g., Quarkus applications).

A complete discussion on migrating to Mutiny 2.0.0 is available at https://smallrye.io/smallrye-mutiny/2.0.0/reference/migrating-to-mutiny-2/

Highlights

• Mutiny 2 is a major release with source and binary incompatible changes to the Mutiny 0.x and 1.x series.
• The upgrade to Mutiny 2.0 is transparent for most code bases that use Mutiny in applications (e.g., Quarkus applications).
• The main highlight of Mutiny 2 is that it is now based on top of the java.util.concurrent.Flow APIs instead of the legacy Reactive Streams APIs.
• The Flow APIs have been part of the JDK since Java 9, and they are the modern Reactive Streams APIs.
• Mutiny remains a faithful implementation of the Reactive Streams specification and passes the Flow variant of the Reactive Streams TCK.
• Deprecated APIs in Mutiny 1.x have been removed, and experimental APIs have been promoted.

Why switch to Flow?

Java 9 adopted the Reactive Streams APIs in java.util.concurrent.Flow, and we think it is about time that the modern Java ecosystem takes advantage of it.

Mutiny remains compliant with the Reactive Streams Test Compliance Kit, so it remains a good citizen when working with other Reactive Streams libraries.

What if I need to use legacy Reactive Streams libraries?

We cover the various cases in our migration guide to Mutiny 2.0.

The short version is that if you have third-party libraries that use the legacy Reactive Streams APIs then you can always use adapters such as those from the Mutiny Zero project

Note that Mutiny provides direct support for RxJava 3 and Reactor, see https://smallrye.io/smallrye-mutiny/2.0.0/guides/converters/ for more details.