3 ms·
I'm confused about calling SQS a many to one service. One of the use cases I've seen (and that is endorsed by AWS) is a worker queue, where someone puts a job i
by __david__ 4y ago
I'm confused about calling SQS a many to one service. One of the use cases I've seen (and that is endorsed by AWS) is a worker queue, where someone puts a job into the queue and there's a whole bunch of workers waiting. One of the workers grabs a message, processes it and then deletes it. That seems like a many to many service to me… Or maybe a many-to-one-of-many service?
- zyberzero 4y agoYou're kind of on it. > One of workers the grabs a message, processes it and then deletes it. If I understood it correctly, in SQS, a message can only be handled by one worker, while SNS can have several workers processing the same message (let's say one worker ingesting the message for system A and another worker to ingest the same message in system B).