[rabbitmq-discuss] Configuration strategy

[Brian Reischl]

You could create all the exchanges, queues and bindings from the admin UI, 
or using some dedicated configurator program or script. Then the actual 
applications could use the Passive forms of the exchange & queue 
declaration functions, which don't require them to know anything beyond the 
names of the queues or exchanges they want to use. 

But I'm certainly no expert, so there may be other options out there. 

On Wednesday, November 27, 2013 2:41:53 PM UTC-7, Adrien Brault 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) ?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131202/a6806f3b/attachment.html>