Publish/subscribe mechanisms that has multiple receivers.

▪ Producer service publish a message and it consumes from

several microservices by subscribing message on the

message broker system.

▪ Publisher don't need to know any subscriber, no any

dependecy with communication parties.

▪ one-to-many (topic) implementation has Multiple receivers. Each

request can be processed by zero to multiple receivers.

▪ Publish/subscribe used in patterns Event-driven microservices

architecture.

▪ Message broker system is publishing events between multiple

microservices, subscribing these events in an async way.

▪ Messages are available to all subscribers and the topic can

have more than one subscriber.

▪ The message remains persistent in a topic until they are deleted.

▪ Kafka, RabbitMQ or Amazon SNS and EventBridge

https://medium.com/design-microservices-architecture-with-patterns/microservices-asynchronous-message-based-communication-6643bee06123