A message broker is an infrastructure service that receives messages from senders, stores them, and eventually delivers them to receivers. It typically implements a message channel, an abstraction of the messaging technology. section 8.3.1
Choose the channel type to match the interaction: point-to-point delivers each message to one consumer, while publish-subscribe delivers it to all subscribers. Commands commonly use point-to-point channels; events commonly use publish-subscribe channels. Brokers such as RabbitMQ, Apache Kafka, and AWS SQS make different trade-offs. section 8.3.1
Figure 8.12 The business logic in the sender invokes a sending port interface, which is implemented by the message sender’s adapter. The message sender sends a message to a receiver via a message channel. The message channel is an abstraction of messaging infrastructure. A message handler adapter in the receiver is invoked to handle the message. It invokes the receiving port interface implemented by the receiver’s business logic.
Trace the message path from sender business logic, through an adapter and channel, to the receiver’s handler and business logic. section 8.3.1





