Advantage of Publishing Message to SNS rather directly pushing to SQS

Question

I am currently building a microservices based backend for my E-Commerce Setup

I need to push all the transactions to a Queue Service, but AWS documentation says that I should publish my message to SNS and then subscribe my queue to a topic

but in SQS documentation there is also a way to send message directly to SQS

*PS: I have already searched stackoverflow but none of the question answers for my specific use case so why are there two solutions for the same thing and need to use SNS and pay extra money

Bloodstream

Answer 1

One reason for that is that you can very easily scale your architecture if you publish to SNS first. This is due to being able to implement fanout scenario:

Now you may only need your msg in a single SQS queue. But later you may want to add second one to process same messages, also maybe invoke some lambda functions independently from your queue, or send them as well to some HTTP endpoint.

Anthelmintic