RabbitMQ Message Routing

RabbitMQ message routing is the process by which a published message is matched against exchange bindings and delivered to one or more queues based on routing keys and exchange type.

Unlike Kafka's log-based model, RabbitMQ is a message broker built on AMQP. Producers never publish directly to queues — they publish to an exchange, and the exchange applies routing logic to forward the message to zero or more bound queues. This indirection is what gives RabbitMQ its flexible routing model.

RabbitMQ ships with four built-in exchange types. A direct exchange routes a message to queues whose binding key exactly matches the message's routing key — ideal for task queues. A fanout exchange ignores routing keys entirely and broadcasts the message to all bound queues, powering Pub Sub Messaging scenarios. A topic exchange uses wildcard patterns (* matches one word, # matches zero or more) enabling flexible hierarchical routing like orders.europe.#. A headers exchange routes on message header attributes instead of routing keys.

Once a message lands in a queue, consumers subscribe and acknowledge. RabbitMQ tracks unacknowledged messages and re-queues them if a consumer disconnects without acking — providing at-least-once delivery by default. Combine this with a Dead Letter Queue for messages that exhaust their retry budget, and Message Queue Retry for controlled backoff between attempts.

This diagram shows a topic exchange routing order events by region to region-specific queues, while a fanout exchange broadcasts audit events to all bound listeners simultaneously.