What is the difference between the point-to-point pattern and the publish-subscribe pattern?

Question

Accepted Answer

Point-to-point and publish-subscribe are two fundamental messaging communication patterns.

In the point-to-point pattern, a message is consumed by exactly one consumer. The producer sends a message to a queue. Multiple consumers can listen to this queue, but each message is only processed by one of them. This is the classic queue model.

This pattern is ideal for task distribution. For example, a job queue where multiple workers each take one job. Each e-commerce order should only be processed once, even if multiple workers are available.

In the publish-subscribe pattern, or pub/sub, a message is distributed to all interested subscribers. The producer publishes a message to a topic or channel. All consumers subscribed to that topic receive a copy of the message.

This pattern is ideal for event broadcasting. For example, when a user signs up, multiple services need to react: the email service sends a welcome message, the analytics service records the event, the CRM service creates a customer record. Each receives the same event and acts according to its responsibility.

In summary, point-to-point for one message equals one processing, pub/sub for one message equals multiple processings.

RabbitMQ supports both patterns via different exchange types. Kafka is natively pub/sub oriented with its consumer groups that also enable point-to-point within a group.