Inspection status updates for one parcel must process in order, but citywide throughput still matters. Which messaging choice best matches that tradeoff?
Select an answer to reveal the explanation.
Short Explanation
One parcel's status changes are like chapters in the same book—they have to stay in order—while other parcels can race ahead. FIFO with a per-parcel MessageGroupId gives that ordering without forcing the whole city into a single file. Standard SQS, unordered SNS, and random S3 prefixes won't protect per-parcel sequence.
Full Explanation
SQS FIFO queues (and similarly ordered streams) provide per-message-group ordering, so using the parcel id as MessageGroupId preserves sequence for that entity while other groups continue in parallel. Standard queues maximize throughput but do not guarantee order. Unordered SNS and random S3 prefixes do not provide broker-level per-entity ordering.