[rabbitmq-discuss] RabbitMQ vs Spread vs QWIDS

Fri Sep 18 13:53:20 BST 2009

I find http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Notes good.
 They don't mention the tools you mention, however.
You've not given any detail to the type of app or use you have, and so it's
difficult to compare them for you. QWIDS seems to be an odd choice as CORBA
went out with the 90's for good reason.  Both Spread and QWIDS seem more
like a message bus, as opposed to a message broker.

In spread you tell a program to join a spread group, then you send messages
and everything in that group gets the message and processes it.  In RabbitMQ
there are multiple workflows.  You can send messages with routing
information, queue up messages for later consumption, use client side
throttling to only receive messages when you need them, etc.

Honestly you should look at your problem area, what you're going to use
RabbitMQ for, and if you need something like RabbitMQ or you need something
like Spread.  I don't seem them as competing for the same space.
Regards,

Gavin

On Fri, Sep 18, 2009 at 8:36 AM, Laurent Frobert <frobert at emsc-csem.org>wrote:

>
> Hi,
>
> my boss wants me to explain why i want to choose RabbitMQ instead of Spread
> (http://www.spread.org/) or QWIDS (http://www.isti2.com/QWIDS/).
> Reason for him,  is that Spread and QWIDS are well used in other production
> environment,
> so, what rabbitmq can give more ?
>
>
> could you help me, thanks
>
> Laurent Frobert
> www.emsc-csem.org
> --
> View this message in context:
> http://www.nabble.com/RabbitMQ-vs-Spread-vs-QWIDS-tp25507940p25507940.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://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/20090918/89a7e1a6/attachment.htm 