Reactive architecture
Reactive architecture is a software architecture organized around asynchronous, nonblocking communication and processing that responds to events over time.
Grokking Simplicity
A software architecture pattern centered on asynchronous communication and systems that respond to changing events or conditions.
- How it is used
- Structures web services and user interfaces around event responses, especially when multiple causes should drive common effects.
- How deep it goes
- Explains event-driven sequencing, pipelines, mutable state, resource-separated timelines, and tradeoffs, stopping short of implementation code.
- Examples
- Uses shopping-cart indicators, ValueCell watchers, FormulaCell totals, document processing, and user notifications as concrete cases.
- What you can do after
- Apply it to decouple causes from effects, compose action pipelines, and design flexible event-driven timelines.
Read how Grokking Simplicity explains reactive architecture →
Microservices Patterns, Second Edition
Reactive design structures software around asynchronous, nonblocking abstractions that represent and compose results over time.
- How it is used
- Supports maintainable, performant API composers when provider calls mix parallel work with sequential dependencies.
- How deep it goes
- Names CompletableFuture, Mono, and Flux, but leaves their implementation and composition mechanics unspecified.
- Examples
- Uses the findOrder() system query to illustrate provider calls that can run in parallel.
Read how Microservices Patterns, Second Edition explains reactive architecture →
Also covered in
Related concepts
- handleruses · A handler is a software routine or component invoked to process an event, request, message, or other input.
- hexagonal architecturepart of · Hexagonal architecture is a software architecture pattern that isolates an application's core logic behind ports and connects external systems through adapters.
- couplinguses · Coupling is the degree of interdependence between software components, including their dependencies on one another’s structure, behavior, or availability.
- structured concurrencyalternative to · Structured concurrency is a concurrency model that scopes related concurrent tasks within a hierarchy so their lifetimes and failures are managed together.
- pipelineuses · A pipeline is an ordered sequence of connected processing stages through which data or work flows, with each stage passing or transforming its output for subsequent stages.
Questions about reactive architecture
What is reactive architecture?
Reactive architecture is a software architecture organized around asynchronous, nonblocking communication and processing that responds to events over time.
Which Manning books explain reactive architecture?
Grokking Simplicity and Microservices Patterns, Second Edition.
What is the difference between reactive architecture and structured concurrency?
Reactive architecture is a software architecture organized around asynchronous, nonblocking communication and processing that responds to events over time. Structured concurrency is a concurrency model that scopes related concurrent tasks within a hierarchy so their lifetimes and failures are managed together.
What is reactive architecture part of?
Reactive architecture is part of hexagonal architecture. Hexagonal architecture is a software architecture pattern that isolates an application's core logic behind ports and connects external systems through adapters.
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.

