[rabbitmq-discuss] Configuration strategy

Emile Joubert emile at rabbitmq.com
Fri Nov 29 09:26:29 GMT 2013

To add to what Brett said, you can withhold permissions to prevent
clients from managing broker resources. Durable resources that are
defined by an administrator will remain in place. You can also set
resources up using the management plugin:



On 28/11/13 00:23, Brett Cameron wrote:
> Adrien,
> While AMQP allows suitably privileged clients (producers, consumers) to
> perform some configuration functions, you certainly do not have to
> design things to work in this way. For example, you could use a facility
> such as the RabbitMQ management plugin to create queues, exchanges, and
> bindings, and give your producers and consumers just the permissions
> they need in order to publish and consume messages - it's entirely up to
> you and your particular needs/requirements.
> Brett
> On Thu, Nov 28, 2013 at 10:41 AM, Adrien Brault <monsti at gmail.com
> <mailto:monsti at gmail.com>> wrote:
>     Hey,
>     I've read the getting started tutorials and am bothered with one
>     aspect: publishers and consumers configures rabbitmq. I understand
>     that those configuration requests are idempotent, however it seems
>     weird to let the application(s) configure rabbitmq.
>     I don't think a publisher should be aware of the exchange type, and
>     a consumer should not be aware of bindings. Though I understand that
>     some pattern requires the application to create
>     exchanges/queues/binding (like RPC).
>     Is there a tool to have some configuration file for the server ?
>     My goal would be that publishers only know what kind of message to
>     send to a specific exchange, and consumer know what kind of message
>     to get from a specific queue.
>     What do you think ? How do you handle the queue/exchange creation
>     and binding logic in big application(s) ?

More information about the rabbitmq-discuss mailing list