reactive-streams/reactive-streams-jvm

Health v2 · maintenance only

Flags: no_releases

Adoption not part of the score

4879 stars · 531 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

The Reactive Streams specification for the JVM, defining a minimal set of interfaces (Publisher, Subscriber, Subscription, Processor) for asynchronous stream processing with non-blocking backpressure. It includes a Technology Compatibility Kit (TCK) for verifying that implementations conform to the specification.

Use cases

• implement a reactive stream library that interoperates with other JVM stream libraries
• verify my stream implementation handles backpressure correctly
• understand the reactive streams specification rules
• test my publisher and subscriber against a conformance suite
• build asynchronous data pipelines without overwhelming consumers
• migrate between reactive libraries using the java.util.concurrent.Flow adapter

When to choose

• you are building or validating a reactive stream implementation on the JVM
• you need a standard interface so different stream libraries can interoperate
• you need a TCK to certify conformance to the Reactive Streams spec

When to avoid

• you want a full reactive programming library with operators like map and filter - use Project Reactor, RxJava, or Akka Streams instead
• you need end-user stream processing tools rather than a specification and interfaces
• you are not working on the JVM or a Flow-compatible environment

Facets

library · maturity stable

streaming concurrency testing developer-tools microservices jvm reactive-streams backpressure specification tck asynchronous flow-api real-time

Member repositories

For agents

markdown · JSON · MCP: product_card(name="reactive-streams/reactive-streams-jvm")