Mutiny to be the first major Java reactive programming library to transition from the legacy Reactive Streams APIs to the modern Java Flow APIs #986
jponge
announced in
Announcements
Replies: 1 comment 4 replies
-
Helidon reactive programming library has been based on Java Flow API since version 2.0.0, June 2020. So not really the first... |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Mutiny is well on its way towards version 2.0.
Be assured that as a user of Mutiny you won’t have to worry much about upgrading your code from
1.x
to2.0
. We are taking binary compatibility very seriously, and each Mutiny release comes with a list of justifications and migration tips for breaking changes if any.So far the main justification for moving to 2.0 has been the transition from Java 8 to Java 11 as a baseline. This is a proper breaking change in semantic versioning parlance, hence the shift of the major version.
But today we are proud to announce that we will make another move towards modern Java by being the first major reactive programming library dropping the dependency on the legacy Reactive Streams APIs, and transitioning to Java Flow (see java.util.concurrent.Flow).
Java Flow was introduced in Java 9 (already a long time ago!) and is isomorphic to the original Reactive Streams APIs. The Reactive Streams TCK (which verifies the correctness of the implementations) ships with a Java Flow variant. The Mutiny Zero project offers adapters between Java Flow and the legacy Reactive Streams APIs, so you will never be locked out as the Java reactive ecosystem should be transitioning towards modern Java.
Beta Was this translation helpful? Give feedback.
All reactions