[Twisted-Python] PB vs JMS

[Jacopo Pecci]

On Mon, Oct 5, 2009 at 8:21 PM, Drew Smathers <drew.smathers at gmail.com> wrote:
>
>
> On Mon, Oct 5, 2009 at 9:14 AM, <jacopo.pecci at gmail.com> wrote:
>>
>> I looked at PB for an architecture with one client distributing some
>> processing to several servers. Now I came across JMS and I have seen that
>> using ActiveMQ with the Stomp protocol there would be a good support for
>> Python.
>> Surprising I couldn’t find any article comparing the two technologies. I
>> wonder if they target different problems (it doesn’t look to me).
>> Is anyone able to sketch advantages of one solution against the other?
>>
>
> I don't think there is a good comparison between the two because they're
> different technologies addressing different problems.  JMS is a messaging
> middleware defined at the Java language API level (hence the need to for
> STOMP protocol and similar adapting layers for use with Python or other
> non-Java languages).  PB is a "secure, easy-to-use Remote Procedure Call
> (RPC) mechanism."
>
> For the system you're descibing it seems like message middleware is more
> what you want.  Unless you want to implement your own load balacing, work
> distribution and failover algorithms?  Another alternative to ActiveMQ is
> RabbitMQ which implements AMQP, which a Python client can speak directly
> without using a limited protocol like STOMP.  There's also handful of good
> AMQP python libs including one for use in Twisted: txamqp.
>
> -Drew
>
>

Thank you Drew.
I should have sketched a bit more:  I have to compute many
self-contained jobs and then elaborate their results.
Jobs are  distributed to many machines and  results are sent back to
the Master. The Master should not wait for all the results to be ready
but should start processing as soon as the first one arrives.  After
all the results have been collected and processed, everything starts
over with newer data.

I have implemented a mock example with PB but if I understand
correctly a messaging system would put me to a higher level of
abstraction taking care of many technicalities. I am now looking at
rabbitmq and txamqp, it is a bit hard to find some documentations but
slowly i am getting the full picture.

Thanks Jacopo