The filtering or routing could be a camel microservice (I have this working on docker AWS today) or I can work up something using the https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html
Our current ActiveMQ uses a Camel content router for managing queue to topics. We setup a single input queue for each application then use camel to route the messages based on a route element in the message header. This keeps the number of application connections down and in case of a queue corruption should not affect other consumers. We are using ActiveMQ in an event based message model today. But the final method is still an open question. I'm still working on getting the architectural model up and running so I can refine the routing and security requirements. btw when will the 2.0.1 release be out? Thanks Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725618.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
