DEV Community

Discussion on: How to use Amazon SQS and SNS for inter-service communication - Part 1

Collapse
 
capnofdship profile image
capnOfdShip

Just curious, in the sample, why do all 4 transfer services have their own queue? Wouldn't 1 queue for the same service (per topic) be enough? Since they would all be writing to the same database and only 1 of them would need to process the message.

Is SNS+ SQS a better approach to microservice communication vs using Kinesis?

We are considering Kinesis thiking it is faster. And we can replay the messages if needed (but we can't think of a scenario for our use case to use it right now).

Collapse
 
jeastham1993 profile image
James Eastham

Hey, thanks for the message. In the specific example, the transfer services would all hold their own internal cache of the team data. So if they shared a queue, once one service had picked up the new queue message the other 3 would never see it.

I don't think that would be the 'best' way to do it n production, I was just providing an example.

I hadn't really looked at Kinesis until recently, but yes I think Kinesis would be a much better provider for this model. It suppors a much more typical pub/sub setup.