The benifit for multiple Queues?

[wangqinghuan <10...@qq.com>]

Artemis has serveral address models. In contrast with Point-to-Point
Messaging , what's the benifits for Point-to-Point Address multiple Queues
.Why defining more than one queue on an address?



--
View this message in context: http://activemq.2283324.n4.nabble.com/The-benifit-for-multiple-Queues-tp4727003.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: The benifit for multiple Queues?

[Justin Bertram <jb...@apache.org>]

To be clear, there's really only 1 addressing model, but that model supports lots of different use-cases.  It's very flexible and supports traditional pub-sub and point-to-point (as you noted).

The benefit of supporting multiple "anycast" queues on a single address is simply that if you need those semantics then they are available to you.  There's nothing inherently "better" about one semantic vs. another.  It's simply about what your use-case requires.


Justin

----- Original Message -----
From: "wangqinghuan" <10...@qq.com>
To: users@activemq.apache.org
Sent: Monday, June 5, 2017 12:07:48 AM
Subject: The benifit  for  multiple Queues?

Artemis has serveral address models. In contrast with Point-to-Point
Messaging , what's the benifits for Point-to-Point Address multiple Queues
.Why defining more than one queue on an address?



--
View this message in context: http://activemq.2283324.n4.nabble.com/The-benifit-for-multiple-Queues-tp4727003.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.