liveBook · Manning

Reactive stream

Reactive Streams is a standard defining interfaces and signaling rules for asynchronous stream processing with nonblocking backpressure between producers and consumers.

How 4 Manning books explain it

Functional Design and Architecture: Examples in Haskell

Reactive Streams is a standard for asynchronous stream processing with non-blocking backpressure between producers and consumers.

How it is used
Organizes changing data and reactions as composable streams in a reactive domain model.
How deep it goes
Defines stream operations and sketches a monitoring scenario, without specifying a protocol or implementation.
Examples
Illustrates a thermometer readings stream and a monitor that stores, validates, and alarms on readings.
What you can do after
Evaluate and understand how a stream-based design separates value production from reactions.

Read how Functional Design and Architecture: Examples in Haskell explains reactive stream →

Spring in Action, Sixth Edition

A stream-processing abstraction that handles data elements as they become available and can represent an unbounded sequence of elements.

How it is used
Introduces reactive streams as pipelines that process data as it becomes available.
How deep it goes
Defines the four Reactive Streams interfaces and introduces a Reactor transformation pipeline.
Examples
Uses a continuous temperature feed and a Mono greeting pipeline to illustrate streaming and transformation.
What you can do after
Evaluate and understand how a Reactor pipeline transforms and delivers data to a subscriber.

Read how Spring in Action, Sixth Edition explains reactive stream →

Quarkus in Action

Reactive Streams is a specification defining interfaces and signaling rules for asynchronous stream processing with nonblocking flow control between producers and consumers.

How it is used
Coordinates nonblocking asynchronous streams and controls producer speed through consumer demand.
How deep it goes
Defines four interfaces and their signaling lifecycle, but discourages direct implementation because protocol conformance is complex.
Examples
Demonstrates Publisher–Subscriber signaling and nonblocking Reservation persistence through Mutiny Uni and reactive database drivers.
What you can do after
Apply it via Mutiny to build nonblocking database and messaging pipelines without implementing Reactive Streams interfaces directly.

Read how Quarkus in Action explains reactive stream →

Spring Security in Action, Second Edition

The Reactive Streams specification defines standard contracts for asynchronous stream processing with bounded resource usage.

How it is used
Supports asynchronous stream processing in reactive applications.
How deep it goes
Explains publisher and subscriber contracts and connects them to Mono, Flux, and Project Reactor.
Examples
Uses a Spring WebFlux HelloController returning Mono<String> and a factory analogy contrasting reactive and non-reactive processing.
What you can do after
Apply it via Project Reactor by modeling endpoint results with Mono or Flux publishers.

Read how Spring Security in Action, Second Edition explains reactive stream →

Also covered in

Related concepts

Questions about reactive stream

What is reactive stream?

Reactive Streams is a standard defining interfaces and signaling rules for asynchronous stream processing with nonblocking backpressure between producers and consumers.

Which Manning books explain reactive stream?

Functional Design and Architecture: Examples in Haskell, Spring in Action, Sixth Edition, Quarkus in Action and Spring Security in Action, Second Edition.

What are the parts of reactive stream?

Reactive stream includes producer and sink node.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.