[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636789#comment-15636789
]
ASF GitHub Bot commented on ARTEMIS-550:
----------------------------------------
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@andytaylor its a couple things beyond just shard topic subscriptions (JMS
2.0). #3 being super critical and highly valuable.
1. Using queues instead of durable topic subscribers allows for all the
add'l queue features-- exclusive consumers, message groups, etc.
2. It separates the producer and the consumers into separate destinations
in an automatic way, without requiring server-side configuration
3. #2 allows you to separate producing message flow from consuming message
flow between brokers across network connectors. We implement both scenarios all
the time: replicate topic production across brokers, but separate consumers..
and the inverse.. share consumers across brokers, but not producers.
Competitor Note: IBM MQ supports the topic -> queue separation. The
advantage ActiveMQ's Virtual Topics have is that it doesn't require server-side
configuration for every topic -> queue setup and every new subscriber.
> 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
>
> Artemis should support virtual topic consumers as alternative to topic
> subscriptions as ActiveMQ itself does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
