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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
