qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suman.Patro-TRN <Suman.Patro-...@lntebg.com>
Subject RE: regarding communication patterns
Date Wed, 07 Oct 2015 06:40:08 GMT
Thank you so much, Gordon.

-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 05 October 2015 14:11
To: users@qpid.apache.org
Subject: Re: regarding communication patterns

On 10/04/2015 11:14 AM, Suman.Patro-TRN wrote:
> 1.Persistence : In rabbitmq ,it is built- in whereas in Qpid, an additional plugin is
required. Is this true?

There are two different brokers available from Qpid. One written in java, one in c++. Both
support pluggable stores, but both now also have an in tree store. For the c++ broker it is
indeed built as a distinct module and needs to be loaded either using the --load-module or
--module-dir options (if you install the broker either from your own build or packages for
your platform, the modules may well be loaded by default). No additional code is needed.

> 2.Routing is available in Rabbitmq but not in Qpid.  Can you Justify?

Not sure what you mean by this. Both the brokers support the old AMQP notion of exchange-queue-binding,
exactly as for RabbitMQ. The c++ broker also allows networks of brokers to be configured,
routing messages between them as needed.

If the latter is what you are looking for however the Qpid Dispatch Router is well worth a
look as it provides a more powerful, robust and yet simpler mechanism. (The router does not
itself provide persistence; it focuses on end-to-end routing not store-and-forward, but can
be combined with brokers to provide persistence for routes that need it).

> 3.Security in RabbitMQ vs Qpid,  difference in approaches that you might have countered
.Which one being more secure?

Both brokers and the router provide SASL based authentication and/or SSL based authentication
and encryption. The c++ broker and the router support GSSAPI/Kerberos on linux.

Both brokers also provide authorisation to further restrict access to different entities within
the  broker (e.g. queues) based on users.

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Larsen & Toubro Limited


This Email may contain confidential or privileged information for the intended recipient (s).
If you are not the intended recipient, please do not use or disseminate the information, notify
the sender and delete it from your system.

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message