liveBook · Manning

Asynchronous architecture

As explained in Microservices Patterns, Second Edition

An asynchronous architecture is an architecture in which communicating components can continue processing without waiting for immediate responses.

Asynchronous architecture lets communicating components continue processing without waiting for immediate responses. Design message channels before choosing a messaging technology. section 8.3.3

Assess each channel’s requirements:

  • Channel type: point-to-point or publish/subscribe. section 8.3.3
  • Delivery guarantees, message ordering, and support for competing consumers. section 8.3.3
  • Persistence, durability, scalability, and end-to-end latency. section 8.3.3
Table 8.4 Each message broker implements the message channel concept in a different way.

Point-to-point channel

Publish-subscribe channel

ActiveMQ

Queue

Topic

Apache Kafka

Topic

Topic

RabbitMQ

Exchange + Queue

Fanout exchange and a queue per consumer

AWS Kinesis

Stream

Stream

AWS SQS

Queue

-

AWS SNS

-

Topic

Compare how ActiveMQ, Apache Kafka, RabbitMQ, AWS Kinesis, AWS SQS, and AWS SNS implement point-to-point and publish-subscribe channels. section 8.3.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Lists channel-selection criteria and broker mappings, while deferring technology choice until requirements are defined.
Examples
Compares broker implementations of point-to-point and publish-subscribe channels.
What you can do after
Evaluate channel requirements and choose a messaging technology suited to each channel.
How it connects
Connects asynchronous messaging to point-to-point and publish-subscribe channels, delivery guarantees, ordering, persistence, and durability.

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.