liveBook · Manning

One-way notification

As explained in Microservices Patterns, Second Edition

A one-way notification is a service interaction in which a client sends a request without expecting or receiving a reply.

A one-way notification is a client-to-service interaction in which the client sends a request without expecting or receiving a reply. It is an asynchronous, one-to-one interaction style. section 8.1.1 section 8.3

With asynchronous messaging, the interaction works as follows:

  • The client sends a message, typically a command, to a point-to-point channel owned by the service. section 8.3.2
  • The service subscribes to that channel and processes the message without sending a reply. section 8.3.2
Table 8.1 The various interaction styles can be characterized in two dimensions: one-to-one vs one-to-many and synchronous vs. asynchronous

one-to-one

one-to-many

Synchronous

Request/response

-

Asynchronous

Asynchronous request/response

One-way notifications

Publish/subscribe

Publish/Async responses

Compare one-way notifications with other interaction styles across synchronous/asynchronous and one-to-one/one-to-many dimensions. section 8.1.1

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the interaction and outlines its messaging implementation with a command, point-to-point channel, subscribing service, and no reply.
What you can do after
Build it from scratch by sending a command to a service-owned point-to-point channel without expecting a reply.
How it connects
Relates one-way notifications to asynchronous messaging, command messages, point-to-point channels, and request/response styles.

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.