liveBook · Manning

Reactive architecture

As explained in Microservices Patterns, Second Edition

Reactive design structures software around asynchronous, nonblocking abstractions that represent and compose results over time.

Reactive design structures software around asynchronous abstractions that represent and compose results over time. In API composition, it helps manage provider calls that combine parallel work with sequential dependencies. section 12.3.3

Choose the concurrency approach to fit the composition:

  • Reactive abstractions include JDK CompletableFuture and Project Reactor Mono or Flux. Structured concurrency is an alternative for managing concurrent tasks within a defined scope. section 12.3.3

How Microservices Patterns, Second Edition covers it

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.
How it connects
Connects API composition with asynchronous service invocation and structured concurrency.

Also explained in

Compare how 2 books explain reactive architecture →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.