Direct Message Behavior and Persistent Message Queue Configuration
Hi all, I am currently exploring the solace message broker and come across two questions.
I am trying to pass images with base64 encoded and direct PubSub is adopted. Since there are some program the subscriber has to run for each message and it takes time. Therefore, I expect there will be a latency for the subscriber to consume the message. I hope that the subscriber will always consume the newest message no matter there is some message it cannot deal with. Is it possible to configure like that? I am a python developer by the way.
I hear there is a term called 'Message Eliding' which I think is relevant. How to configure that in my python script?
Another cases, I have four subscribers and I expect those subscribers only consume the message with a pre-defined message_id pattern. For example subscriberA would only consume the message with the id that give a remainder of 0 when divided by 4. In this case, should I make 4 topics and 4 queues? Is there any better solutions? I hear there is a term called 'partition'
I would be very grateful if someone can help me with these questions. Feel free to let me know if there is anything not clear. Thanks a lot.