5 ms·

Thanks for the reply ... Perhaps ... there is one thing we did not see ... Is there assurance in SQS to ensure that what is first processed is actually what i

Thanks for the reply ... Perhaps ... there is one thing we did not see ... Is there assurance in SQS to ensure that what is first processed is actually what is first? (i.e. process these in the order of the row number - not the order you receive them.) Meaning - typically with outside systems we have a list of messages ... ("we need these 1000 messages processed in order") ... ... with push/pop - we could typically ensure the first message is the first message ... ... For SQS - how do we ever ensure the first message (and every subsequent message) is the actual order we desire? (Not the order the internet arbitrarily delivered them)

doormatt 3y ago
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues-message-order.html https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQS... >The order in which messages are sent and received is strictly preserved and a message is delivered once and remains available until a consumer processes and deletes it. >In addition, FIFO queues support message groups that allow multiple ordered message groups within a single queue. There is no quota to the number of message groups within a FIFO queue.