[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281095#comment-16281095
]
Matt Pavlovich edited comment on ARTEMIS-550 at 12/6/17 11:13 PM:
------------------------------------------------------------------
The 3 key features of Virtual Topics in ActiveMQ 5.x that differentiate it from
just being 'JMS 2.0 topics':
# Consumption is in a different destination altogether
# Consumption is handled by a queue-- which supports wider range of consuming
options-- exclusive consumer, etc.
# Client-consumers drive the behavior without the need for server-side
configuration
Use case 1:
Cross-cluster pub-sub, localized consumption
* Broker A is configured to include topic://vTopic.> in network of brokers AND
exclude queue://vTopicConsumer.> in network connector to Broker B.
Use case 2:
Localized pub-sub, cross-cluster consumption
* Broker A is configured to exclude topic://vTopic.> in network of brokers AND
include queue://vTopicConsumer.> in network connector to Broker B.
Since publishing and subscribing is done in different destinations, additional
messaging patterns are possible. For competitive and comparison purposes it
should be noted that IBM MQ has the exact same feature.
was (Author: mattrpav):
The key features of Virtual Topics in ActiveMQ 5.x that differentiate it from
just being 'JMS 2.0 topics' is that the consumption is in a different
destination altogether, and that consumption is handled by a queue-- which
supports wider range of consuming options-- exclusive consumer, etc.
Use case 1:
Cross-cluster pub-sub, localized consumption
* Broker A is configured to include topic://vTopic.> in network of brokers AND
exclude queue://vTopicConsumer.> in network connector to Broker B.
Use case 2:
Localized pub-sub, cross-cluster consumption
* Broker A is configured to exclude topic://vTopic.> in network of brokers AND
include queue://vTopicConsumer.> in network connector to Broker B.
Since publishing and subscribing is done in different destinations, additional
messaging patterns are possible. For competitive and comparison purposes it
should be noted that IBM MQ has the exact same feature.
> Add support for virtual topic consumers
> ---------------------------------------
>
> Key: ARTEMIS-550
> URL: https://issues.apache.org/jira/browse/ARTEMIS-550
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 1.3.0
> Reporter: Benjamin Graf
> Assignee: Martyn Taylor
>
> Artemis should support virtual topic consumers as alternative to topic
> subscriptions as ActiveMQ itself does.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
