Reactive stream
Reactive Streams is a standard defining interfaces and signaling rules for asynchronous stream processing with nonblocking backpressure between producers and consumers.
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 recurring device input and downstream reactions into a reactive domain model.
- How deep it goes
- Defines event streams and their transformations, then sketches a producer-monitor workflow rather than an implementation.
- Examples
- Uses periodic thermometer readings, Kelvin conversion, validation, storage, logging, and alarms in paired streams.
- What you can do after
- Apply it to separate recurring input from validation, persistence, and notification 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
- Frames asynchronous processing of arriving data, including potentially endless sequences, without requiring the entire dataset up front.
- How deep it goes
- Defines the four specification interfaces and backpressure, then illustrates a Reactor pipeline without developing an implementation of the interfaces.
- Examples
- Uses an endless temperature feed, a garden-hose analogy, interface listings, and a Mono greeting pipeline.
- What you can do after
- Apply it via Reactor’s Mono to compose and subscribe to a simple pipeline, while distinguishing Mono from Flux.
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.
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 →
Related concepts
- Project Reactorimplemented by · Project Reactor is a JVM reactive programming library providing asynchronous, nonblocking types and operators for composing data sequences with backpressure.
- Mutinyimplemented by · Mutiny, also known as SmallRye Mutiny, is a Java reactive programming library providing asynchronous types and APIs for composing event-driven operations.
- producerhas part · A producer is an entity or process that creates or supplies values, data, messages, events, or work for another entity to consume.
- sink nodehas part · A sink node is a terminal or receiving component in a data or flow system that accepts incoming data, messages, or flow for consumption, processing, or storage.
- reactive messagingused by · Reactive messaging is an asynchronous messaging approach in which messages are processed through reactive streams and communicated between application components or services.
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.