What is the Competing Consumers pattern?
The Competing Consumers pattern runs multiple consumer instances on the same queue or partition set. Each worker concurrently pulls distinct messages, dynamically scaling throughput to absorb ingress traffic spikes.
Answered in
Seven Message Broker Patterns: Data Consistency, Workload Management, and VisibilityMaster essential message broker patterns: Transactional Outbox, Idempotent Consumer, Dead Letter Queues, Competing Consumers, and Priority Queues.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the difference between a Push CDN and a Pull CDN?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.