Clarification on queue use-case
I have a publisher posting messages to various topics.
I have no idea what applications are going to read from these topics. These are for example sales orders, so durable messages.
I had the following in mind: create a queue and let subscribers read from that. However, to my understanding, the message queue can only be processed once. It is not possible to have multiple applications read from the same queue in their own pace.
Should every application make their own queue, then add subscriptions to collect events from various topics, and finally read from their own queue?
Is solace smart enough to not duplicate all these messages on disk for every application that's creating a queue?
Or is an other approach better to have multiple applications consume the same messages for their own use?