Back to Catalog
Integration
Messaging Endpoints
Message Dispatcher
Central dispatcher receives messages and hands them off to specific handlers — controlled fan-out to workers.
Intent & Description
Real-world Use Case
Multi-priority job queue — Dispatcher receives job messages and routes HIGH priority jobs to a dedicated premium-workers pool, NORMAL jobs to general-workers pool. Premium workers are never waiting on normal jobs. Simple Competing Consumers on one queue would not give this control.
Source
📌 TL;DR
Message Dispatcher = smarter-than-random worker pool management. Routes messages to the right handler, manages priorities. Use when Competing Consumers is too blunt.
Advantages
- Adds routing and prioritization logic to consumer distribution
- Central control point for handler lifecycle and load management
- Supports heterogeneous handler pools (different handlers for different message types)
- Enables backpressure and throttling at the distribution layer
Disadvantages
- Dispatcher is a single point of failure — must be made HA
- More complex than simple Competing Consumers
- Dispatcher logic can become over-complicated
- Adds a processing hop compared to direct consumption