I have a scenario where I want to publish actions in a single channel and want multiple groups of consumers compete for actions they are specialized to process.
E.g. 2 types of actions with an attribute indicating their type:
- Complex action
- Simple action
Then, I need 2 groups of consumers (that I can scale in/out based on the load) to process 2 types of actions.
The solution should be as simple/cheap as possible.
Options I considered so far: Azure Service Bus, RabbitMQ, Kafka.
Azure SB approach I came up with seems a bit complex: Single topic with subscribers sending filtered actions to 2 separate queues and consumers processing actions.
Is there a simpler/cheaper ootb approach in azure?
Suggestions?