[rabbitmq-discuss] Configuration strategy
brett.r.cameron at gmail.com
Thu Nov 28 00:23:40 GMT 2013
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
On Thu, Nov 28, 2013 at 10:41 AM, Adrien Brault <monsti at gmail.com> wrote:
> 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
> 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) ?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss