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
