Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    SQS cannot send a message to many systems as it does not fan out the messages. Yes, many pollers can pull messages from it, but if one the consumers deletes the message then other subscribers won't be able to consume the same message again. SNS is preferred over SQS if you want to achieve a fan out pattern. Also, if the visibilityTimeout is set, than no other systems will be able to consume the message once it's being processed by other system. Commented Jun 7, 2019 at 8:09
  • 2
    A common pattern is to use SNS to publish messages to Amazon SQS queues to reliably send messages to one or many system components asynchronously. Reference from aws.amazon.com/sns/faqs Commented Jun 7, 2019 at 11:59
  • 1
    If that's what you meant (SNS -> multiple SQS queues) then please edit your answer and I will happily remove my downvote. The way you put it, it sounds like SQS can fan out. Commented Jun 7, 2019 at 12:52
  • 1
    Yes.. thats where the confusion was. I have edited it .. Thanks :) Commented Jun 7, 2019 at 14:31
  • This is a start, but the question was about the differences, etc.: "When would I use SNS versus SQS, and why are they always coupled together?" Perhaps address that more directly? You can edit your answer (without "Edit:", "Update:", or similar - the answer should appear as if it was written today). Commented Feb 2, 2021 at 10:41