When would I use a fanout exchange?
When every interested consumer needs every message and routing keys are irrelevant: broadcasting cache invalidations, pushing notifications to several independent services, or feeding both a search indexer and an audit log from the same event. Each bound queue gets its own copy.
Answered in
RabbitMQ Routing: Direct, Topic, Fanout, and Why Producers Never Touch QueuesIn RabbitMQ a producer publishes to an exchange, not a queue. Bindings and exchange type decide where each message lands. Here is how the routing really works.
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.