Back to Catalog
Integration
Message Channels
Point-to-Point Channel
Each message goes to exactly one consumer — a queue, not a broadcast.
Intent & Description
Real-world Use Case
Job processing queue — 500 background jobs are published to a processing queue. 20 worker instances compete for jobs. Each job is processed by exactly one worker. No duplicate processing. Worker crashes mid-job — broker redelivers the unacknowledged job to another worker.
Source
📌 TL;DR
Point-to-Point Channel = each message gets one consumer. Queue semantics, competing workers, load-balanced by the broker. The go-to for task queues, job processing, and command dispatch.
Advantages
- Exactly-once consumption guarantee (per message, per delivery)
- Natural load balancing via Competing Consumers
- Work distribution without coordination between consumers
- Built-in retry on consumer failure (via message redelivery)
Disadvantages
- No broadcast — if multiple systems need the same message, Pub-Sub is needed
- Message ordering not guaranteed with multiple competing consumers
- Consumer coordination needed if strict ordering or exclusivity per entity is required
- Dead-lettering unprocessable messages needs explicit configuration