SQS is fairly consistent with the order in which messages come in.
However, let's say that Grand Central crashes on a message, so said message ends up rejoining the queue later. That can mean that an update to a story can be performed, but then GC pulls in that old message that it initially failed on and performs an update that's older than the last one.
It's an edgy case, but it would be good to make sure that GC never acts upon messages that are older than the last one processed for a particular piece of content.
SQS is fairly consistent with the order in which messages come in.
However, let's say that Grand Central crashes on a message, so said message ends up rejoining the queue later. That can mean that an update to a story can be performed, but then GC pulls in that old message that it initially failed on and performs an update that's older than the last one.
It's an edgy case, but it would be good to make sure that GC never acts upon messages that are older than the last one processed for a particular piece of content.