Naming Queues - messagebus/lapine GitHub Wiki

It can be helpful when naming queues to include an application identifier. This not only ensures that different applications do not register duplicate queue names (possibly for different routing keys), but also helps when debugging.

queues:
 - q: thing.happened
   topic: my.topic
   routing_key: my.thing.happened
   handlers:
     - ThingHappenedWorker
 - q: my-app.thing.happened
   topic: my.topic
   routing_key: my.thing.happened
   handlers:
     - ThingHappenedWorker

If you have an alert to email when queues are backed up in RabbitMQ (for instance in Sensu or Nagios), the first queue may be ambiguous if the developer on call is not familiar with my-app. The second queue is less ambiguous, and may save precious debugging time.

Note that queues are registered as persistent, so if you change a queue name someone will need to manually delete the old queue in RabbitMQ.