liveBook · Manning

Request-response API

A request-response API is an interaction pattern in which a requester sends a request to a provider and receives a corresponding response.

How 2 Manning books explain it

Spring in Action, Sixth Edition

A request-response model is a communication pattern in which one party sends a request and waits for a corresponding response.

How it is used
Provides a single-reply communication pattern for clients and servers, including HTTP-style exchanges implemented with RSocket.
How deep it goes
Defines the exchange and works through a Spring server and client, including routing, payloads, response retrieval, and subscription.
Examples
Uses a greeting controller and an RSocketRequester that sends “Hello RSocket!” and logs the returned greeting.
What you can do after
Apply it via Spring RSocket controllers and RSocketRequester to send a routed request and handle one reactive reply.

Read how Spring in Action, Sixth Edition explains request-response API →

Kafka for Architects

A request-response pattern is a communication pattern in which one service sends a request and another service returns a corresponding response.

How it is used
Frames direct service interaction as an alternative to event-driven and publish-subscribe communication.
How deep it goes
Explains correlation and failure hazards, but stops short of detailing recovery strategies beyond identifying implementation approaches.
Examples
Uses correlation headers, response topics, partitions, service instances, and failure-reassignment scenarios.
What you can do after
Apply it via Spring Kafka while accounting for correlation, response routing, and lost request context after consumer failure.

Read how Kafka for Architects explains request-response API →

Related concepts

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.