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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.