Hi @gauravvats ,
I agree with @TomF that the simplest solution here is likely to publish your events to topics and have one queue which subscribes to all of the topics. If you’re not familiar with how this works @Aaron made a great video which will hopefully help: https://www.youtube.com/watch?v=PP1nNlgERQI&list=PLY1Ks8JEfJR57vCkrQK0Y9bn8DKNMMJI_&ab_channel=Solace
As Tom mentioned, on the consumer side if you need helping understanding what event you’re receiving then you could either parse that out of the topic or another option would be to have the publisher add a user property (key/value pair) to the event which identifies what it is. The consumer can then look at that to identify which operation to invoke.
Hope that helps