Message Queue and Message Bus

This is one of the most common questions we often encounter when chatting with friends or searching for something on the Internet. This article will explain these two confusing terms.

The definition of a message queue is to receive a series of messages from one application and deliver them to one or more other applications in a first-in-first-out (FIFO) manner. Each application can have its own queue. Events created by the application write certain things to the queue. A message queue consists of publishers and consumers. Something called a publisher leaves messages on a queue. Consumers also acquire and process them. These are common patterns used in distributed systems.

These are the most common and are used as message queues. RabbitMQ, Kafka, ActiveMQ, AmazonSQS, IronMQ, Redis.?

The message bus is also known as the service bus. A message bus provides a messaging infrastructure for one or more applications to deliver messages to one or more other applications.

Message Bus does not guarantee first in, first out. Message bus subscribers can receive published messages without knowing the publisher. These patterns are also known as Pub/Sub. Messages are published to the bus by a send API, and a receive API subscribed to any message type retrieves the appropriate message.

These are the best known and are also used as message queues. Microsoft Azure Service Bus, Oracle Enterprise Service Bus, Rabbitmq (MassTransit)?

Publisher applications contribute their own status updates to the message bus. Agents interested in this message receive these status updates from the message bus.?