Consume a persistent Message from Queue or Subscription
After some studies, and proof of concept, I have a question about the consuming side, since the producer side is very clear to me.
Let's say I need to save files using Solace Message Broker, so I have the following configuration for producer, topic, and queue:
The producer sends a message with the Topic "storage/document/save-document". This topic is assigned to Queue "storage.document.save-document.queue" via Solace REST API. So, when a message is sent to this topic, it stays in this queue until a consumer consumes it.
Here, you say the best practice is consuming from a Queue, is that always so? In this case, what about the flexibility to plug an analytics system here to collect statistics? How I should build this?
I can't use the wildcards to consume persistent messages, for instance, create a consumer to log all storage events matching a range of topics: "storage/>"? How I should build this?
Is the subscription available in the Solace REST API between a topic and a queue, the same called here? `jcsmpSession.addSubscription(queue, topic, JCSMPSession.WAIT_FOR_CONFIRM)?`