[rabbitmq-discuss] forwarding between vHosts

[Laing, Michael]

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> 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>
> 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> 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
> >> 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
> >
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131026/2c46f35c/attachment.htm>