Apr 22, 2021
Why sqs is not well suited for multiple consumers? It is, it’s just needs clarification what we multiply or make a more strict naming “consumer” vs “all message consumer” or anything :) If we are aiming for a concurrent consumption of a single message queue we can do it, consumers will just process different messages, but what is wrong with that?
If we want to independently process messages then it’s indeed not well suited cause it works more less like a rabbitmq consumers with same group ID.
I guess for many people term consumer is every app that connects to a queue, not every type of app that wants to ready messages from the queue.