[rabbitmq-discuss] forwarding between vHosts
Julian Lyndon-Smith
julian+rabbitmq at dotr.com
Mon Oct 28 09:21:54 GMT 2013
that's great news .. when ? ;)
Also, do shovels allow you to move messages based on content ?
On 28 October 2013 09:03, Simon MacMullen <simon at rabbitmq.com> wrote:
> At some point in the future - hopefully 3.3.0 - we intend to allow for
> dynamic shovels too, by the way.
>
> Cheers, Simon
>
> On 26/10/2013 10:29PM, Laing, Michael wrote:
>>
>> Hmm - shovels are best for mostly static setups currently...
>>
>> I experimented as well using federation awhile back, and that is
>> dynamically configurable by setting policies using the mgt api.
>>
>> It worked, but at the time federation was new, and I found shovels to be
>> rugged and suitable for my use case. In our next internal release I
>> think I will start deploying some federated links however.
>>
>> So I would try federation if you really need to architect this way.
>>
>> Good luck!
>>
>> Michael
>>
>>
>>
>> On Sat, Oct 26, 2013 at 5:09 PM, Julian Lyndon-Smith
>> <julian+rabbitmq at dotr.com <mailto:julian+rabbitmq at dotr.com>> wrote:
>>
>> Thanks for the info. I still have a couple of questions ;)
>>
>> Is there an api for adding shovels ? The tenants are dynamic (ie they
>> can be created at any time, and not known in advance) Or do you have
>> to manually edit a file ?
>>
>> You have to restart the server to add a new shovel ? Really ? If
>> that's a case, it's a no go - data is flying around from several
>> sources and I couldn't stop 20 clients in order to add a 21st.
>>
>> Julian
>>
>>
>>
>> On 26 October 2013 22:00, Laing, Michael <michael.laing at nytimes.com
>> <mailto:michael.laing at nytimes.com>> wrote:
>> > We use shovels for inter-vhost communication like that.
>> >
>> > Easy and quick. Except you have to restart a cluster member to
>> pick up the
>> > config...
>> >
>> > Michael
>> >
>> >
>> > On Sat, Oct 26, 2013 at 4:33 PM, Julian Lyndon-Smith
>> > <julian+rabbitmq at dotr.com <mailto:julian%2Brabbitmq at dotr.com>>
>> wrote:
>> >>
>> >> I have a scenario where I need to be able to have a multi-tenant
>> MQ
>> >> server, so I started using vHosts.
>> >>
>> >> However, I also need to be able to route / transfer / forward
>> messages
>> >> from a stomp client that is sending to the / vhost to another
>> vhost
>> >> based on the queue that the message was sent to
>> >>
>> >> for example, the stomp client sends to /queue/api/foo.bar , I
>> want to
>> >> send the message to vHost foo
>> >>
>> >> I can , obviously create a stomp client for each tenant, but that
>> >> becomes real expensive in resources very quickly and was hoping
>> that
>> >> there would be a better way
>> >>
>> >> Many thanks
>> >>
>> >> Julian
>> >> _______________________________________________
>> >> rabbitmq-discuss mailing list
>> >> rabbitmq-discuss at lists.rabbitmq.com
>> <mailto:rabbitmq-discuss at lists.rabbitmq.com>
>> >>
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> >
>> >
>> >
>> > _______________________________________________
>> > rabbitmq-discuss mailing list
>> > rabbitmq-discuss at lists.rabbitmq.com
>> <mailto:rabbitmq-discuss at lists.rabbitmq.com>
>> >
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> >
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> <mailto:rabbitmq-discuss at lists.rabbitmq.com>
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>>
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
More information about the rabbitmq-discuss
mailing list