Dev
RabbitMQ Exchange Generator
Used by developers, writers, and creators worldwide.
A RabbitMQ exchange generator gives you the rabbitmqadmin commands to declare an exchange, a queue, and the binding between them, so you wire up messaging topology without clicking through the management UI. Pick the exchange type — direct, topic, fanout, or headers — and name it, and it returns three durable declarations plus a binding with a routing key that fits the type, such as a wildcard for a topic exchange or no key for a fanout. Backend engineers use it to set up a messaging route, recall the binding rules each exchange type follows, or script repeatable topology. It runs in your browser and generates instantly. Paste the commands into a shell where rabbitmqadmin is configured, change the queue and routing key, and run them. Declaring everything durable means your topology and messages survive a broker restart, which is what you want in production.
Read the complete guide — 4 min read
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick the exchange type.
- Name the exchange.
- Click Generate to produce the rabbitmqadmin commands.
- Paste them into a configured shell and adjust the queue and key.
Use Cases
- •Declaring an exchange, queue, and binding from the command line
- •Choosing the right exchange type for a routing pattern
- •Remembering the binding rules each exchange type uses
- •Scripting repeatable RabbitMQ topology for an environment
- •Setting up a messaging route without the management UI
Tips
- →Use a topic exchange when you need flexible wildcard routing.
- →Declare exchanges and queues durable for production.
- →Add a dead-letter exchange to capture rejected messages.
- →Keep routing keys consistent with a clear naming scheme.
FAQ
which exchange type should I pick
Use direct for exact routing-key matches, topic for wildcard patterns like order.*, fanout to broadcast to every bound queue, and headers to route on message attributes. Topic is the most flexible and a common default for event streams.
why declare everything durable
A durable exchange and queue survive a broker restart, and durable plus persistent messages are not lost on a crash. For anything beyond throwaway testing, durable is the setting you want so topology does not vanish.
why does fanout skip the routing key
A fanout exchange ignores routing keys and delivers every message to all bound queues, so the binding needs no key. Direct and topic exchanges use the routing key to decide which queues receive a message.
You might also like
Popular tools from other categories that share themes with this one.