Core Principles of Message Queues: 12 Key Concepts Explained

Hello, I am mikechen. Message queues (MQ) are essential skills for high‑concurrency distributed systems and are frequently asked in major‑company interviews.

Message queues have become the core mechanism for distributed applications, internal communication, and flash‑sale scenarios, offering low coupling, reliable delivery, broadcast, flow control, and eventual consistency.

Whether using RabbitMQ, RocketMQ, ActiveMQ, Kafka, or other solutions, they share basic principles, terminology, and mechanisms, which are summarized here to help you quickly understand MQ technology.

1. Producers, Consumers, Broker, Queue

Producer : Sends messages to the message queue.

Consumer : Receives messages from the message queue.

Broker : The server side (originating from Apache ActiveMQ) that transports messages from producers to consumers.

Queue : A FIFO storage area where messages are kept until consumed or timed out.

2. Design Considerations for the Broker

Message dumping: deliver at an appropriate time or use auxiliary means to ensure final delivery.

Establish a common pattern to satisfy decoupling, eventual consistency, and traffic‑shaping needs.

Conceptually, the broker acts as a message forwarder, turning one RPC into two RPCs (producer → broker → consumer).

In summary, it is two RPCs plus one dump; with consumption acknowledgment it becomes three RPCs.

3. Point‑to‑Point (P2P) Model

The P2P model enables direct communication between a producer and a consumer.

Roles in the P2P model:

Queue (Message Queue)

Sender (Producer)

Receiver (Consumer)

Each message is sent to a specific queue; the receiver pulls messages from that queue. Queues can reside in memory or be persisted until consumption or timeout.

Features

Only one consumer can process a given message.

Producers and consumers are temporally decoupled.

Consumers must acknowledge successful receipt to the queue.

4. Publish/Subscribe (Pub/Sub) Model – Topic

Roles in the Pub/Sub model:

Topic

Publisher

Subscriber

Multiple publishers send messages to a topic, and the system forwards those messages to all subscribed consumers.

Features

A message can have multiple consumers; all subscribers can receive the same message.

Publishers and subscribers have a temporal dependency.

Subscribers must create a subscription before they can consume messages.

Subscribers need to stay online to receive messages.

5. Differences Between P2P and Pub/Sub

In P2P, a producer sends a message to a queue and only one consumer receives it. In Pub/Sub, a publisher sends to a topic and only those subscribers who have subscribed to the topic receive the message.

6. Message Ordering Guarantee

Using the FIFO nature of the queue model ensures that messages are processed in the order they were sent.

7. ACK Mechanism

The ACK (acknowledge) mechanism ensures that a message is not lost: after a consumer processes a message, it sends an ACK to the broker, allowing the broker to delete the message. If the consumer crashes without sending ACK, the broker will redeliver the message to another consumer.

8. Design for Eventual Consistency

Eventual consistency is achieved by recording and compensating: local transactions store business changes and notification messages together; after the broker successfully persists the message, the local transaction can be cleared. Otherwise, a retry mechanism resends the message until it is reliably stored.

9. Transaction Support

Message sending and receiving can participate in a single transaction scope; if any message processing fails, the transaction rolls back and the message returns to the queue for reprocessing.

10. Message Persistence

Enabling persistence ensures that messages survive broker restarts, preventing loss of critical business data.

11. High Availability of Message Queues

Single‑instance brokers are a single point of failure. High‑availability solutions include RabbitMQ mirrored clusters, ActiveMQ with LevelDB + ZooKeeper, and Kafka’s replication mechanism.

12. MQ Selection and Application Scenarios

Choosing the right MQ depends on factors such as throughput, latency, durability, and ecosystem support.

Finally, a free resource is offered: an original 300,000‑word collection of advanced Alibaba architect materials, which can be obtained by adding the author’s WeChat and mentioning “合集”.