You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Suman.Patro-TRN" <Su...@lntebg.com> on 2015/10/02 07:01:49 UTC
regarding communication patterns
Hello,
Is Request/ reply pattern available in qpid 0.34?
Kindly reply.
Thanks and regards,
Suman
Larsen & Toubro Limited
www.larsentoubro.com
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
RE: regarding communication patterns
Posted by "Suman.Patro-TRN" <Su...@lntebg.com>.
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
www.larsentoubro.com
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
Re: regarding communication patterns
Posted by Gordon Sim <gs...@redhat.com>.
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
RE: regarding communication patterns
Posted by "Suman.Patro-TRN" <Su...@lntebg.com>.
Thank you so much Gordon. Your help is highly appreciated as I had no idea about the AMQP 1.0 feature.
There are certain other ambiguities that I would like to get cleared upon:
1.Persistence : In rabbitmq ,it is built- in whereas in Qpid, an additional plugin is required. Is this true?
2.Routing is available in Rabbitmq but not in Qpid. Can you Justify?
3.Security in RabbitMQ vs Qpid, difference in approaches that you might have countered .Which one being more secure?
The above queries are with respect to current versions of Rabbitmq and qpid C++ broker.
Thanks and regards,
Suman
________________________________________
From: Gordon Sim [gsim@redhat.com]
Sent: Friday, October 02, 2015 9:30 PM
To: users@qpid.apache.org
Subject: Re: regarding communication patterns
On 10/02/2015 01:28 PM, Suman.Patro-TRN wrote:
> I would like to know the speed of request reply pattern in Qpid in comparison to YAMI4 broker(wire- level protocol based)
Speed can mean different things here. There is the latency of the
request-response roundtrip and there is the throughput of many of these
if they are sent asynchronously.
I'm not aware of any benchmarks focused specifically on this pattern, so
you would need to do some experimentation yourself.
> , mosquitto broker(mqtt based), rabbit mq(amqp based, zeromq(brokerless solution)
Just as an aside, MQTT doesn't really directly support request-response.
It is designed around pub-sub. You can of course invent a convention on
top of that yourself.
I believe that the various Qpid intermediaries (there is a Java broker,
a c++ broker and a router) would compare very favourably with RabbitMQ
as regards both latency and throughput.
Note also that with AMQP 1.0 you can do direct, non-intermediated
request-response as well, more like the basic REQ-REP pattern in zeromq.
Further, its not too difficult to write your code in such a way that it
can be used wither with direct- or with intermediated- communication.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Larsen & Toubro Limited
www.larsentoubro.com
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
Re: regarding communication patterns
Posted by Gordon Sim <gs...@redhat.com>.
On 10/02/2015 01:28 PM, Suman.Patro-TRN wrote:
> I would like to know the speed of request reply pattern in Qpid in comparison to YAMI4 broker(wire- level protocol based)
Speed can mean different things here. There is the latency of the
request-response roundtrip and there is the throughput of many of these
if they are sent asynchronously.
I'm not aware of any benchmarks focused specifically on this pattern, so
you would need to do some experimentation yourself.
> , mosquitto broker(mqtt based), rabbit mq(amqp based, zeromq(brokerless solution)
Just as an aside, MQTT doesn't really directly support request-response.
It is designed around pub-sub. You can of course invent a convention on
top of that yourself.
I believe that the various Qpid intermediaries (there is a Java broker,
a c++ broker and a router) would compare very favourably with RabbitMQ
as regards both latency and throughput.
Note also that with AMQP 1.0 you can do direct, non-intermediated
request-response as well, more like the basic REQ-REP pattern in zeromq.
Further, its not too difficult to write your code in such a way that it
can be used wither with direct- or with intermediated- communication.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: regarding communication patterns
Posted by "Suman.Patro-TRN" <Su...@lntebg.com>.
Thanks Gordon... but I would like to know the speed of request reply pattern in Qpid in comparison to YAMI4 broker(wire- level protocol based) , mosquitto broker(mqtt based), rabbit mq(amqp based, zeromq(brokerless solution)
Thank and regards,
Suman
-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 02 October 2015 14:33
To: users@qpid.apache.org
Subject: Re: regarding communication patterns
On 10/02/2015 06:01 AM, Suman.Patro-TRN wrote:
> Is Request/ reply pattern available in qpid 0.34?
Yes. Essentially you set a reply-to address to which the 'server' will respond. What client are you using? There may be an example for that already.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org
Larsen & Toubro Limited
www.larsentoubro.com
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
Re: regarding communication patterns
Posted by Gordon Sim <gs...@redhat.com>.
On 10/02/2015 06:01 AM, Suman.Patro-TRN wrote:
> Is Request/ reply pattern available in qpid 0.34?
Yes. Essentially you set a reply-to address to which the 'server' will
respond. What client are you using? There may be an example for that
already.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org