Is there anything I need to do to ensure queue delivery (SQS) at AWS?

0

Assuming that I have 2 microservices "A" and "B" that are communicating via an SQS "F" queue.

Microservice "A" can fall, "B" can also fall, the question is: should I take into account that "F" could also fall?

If I take into account that "F" might fall, I could do something like put the message to be sent to a table in the database and send the asynchronous send via job to "F", but this looks like an overengineering. / p>

According to the link link AWS says this: "Standard queues offer delivery at least once, that is, each message is delivered at least once. "

Should I just rely on SQS availability and track if something is not sent instead of doing something to "secure delivery" to "F"?

    
asked by anonymous 07.11.2018 / 00:04

1 answer

0

Normally there is no need to trace message deliveries, and it would be very difficult to do so more efficiently than SQS. If you need more control over message consumption, it might be more interesting to consider other services, such as Amazon Kinesis. Also note that the message retention limit in SQS is 14 days, messages need to be consumed in this period.

    
08.11.2018 / 09:54