Hello Derek! All very good questions.

1. This BunnyBus supports everything RabbitMQ supports. queue options can be passed in the subscribe() interface. Through that, you can configure for durability.
2. This most certainly provides support for multiple clients feeding off of the same queue. In fact, it is has we scale out our workers in EBS. Say you have a code base setup to subscribe('queueName1'). When you instantiate multiple process for that corresponding code base, they will all feed off of the same queue.
3. BunnyBus does **NOT** name queues for you and it is left to the responsibility of the client. A suggestion would be for you to use the name of the owning package as the name of the queue. We use hapijs plugins for each of our worker types. So that is how we generate our queue names too.