Hi William- A messaging pattern of millions of queues with low volume of messages sounds like an anti-pattern.
Keep in mind that there is overhead for maintaining a queue — indexes, etc — and you’d need a consumer object per-queue residing in the broker. If you add networking-of-brokers to that, you now have fanned out those consumer counts across multiple brokers in the cluster — and you can see the total object count is going to go really high for a low message. ActiveMQ Classic supports composite and wildcard consuming patterns to support significantly dropping that number. Last time I checked, Artemis didn’t support that. There are other patterns to do transmission queues, router-gateway two-layered architectures, etc to accommodate the use case without requiring millions of queues with small number of messages. Additionally, you can look to layer on selectors or use message filter EIP as a layer on top to separate and filter messages without having to have millions of queues. Hope this helps! Thanks, Matt Pavlovich > On Mar 5, 2025, at 12:30 PM, William Crowell <wcrow...@perforce.com.INVALID> > wrote: > > Good afternoon, > > Are there any limitations or concerns with creating millions of topics and > queues within Apache Artemis that have low volumes of messages in each topic > and queue? I do not think there are as I believe Artemis should be able to > handle this use case. Important question is: Is it scalable? > > Regards and have a great day, > > William Crowell > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
