Message Ordering Guarantees

Also Known As

TL;DR

Explanation

Message ordering matters when events must be processed in sequence: UserCreated before UserUpdated, OrderPlaced before OrderShipped. Ordering options: FIFO queues (SQS FIFO, RabbitMQ with single consumer) — strict order but lower throughput. Partitioned logs (Kafka) — order within partition by key; use the entity ID as key (all order events for order 42 go to the same partition). Causal ordering: include a causality token to detect out-of-order processing. Idempotent consumers handle duplicate delivery; sequence numbers detect gaps.

Common Misconception

Why It Matters

Common Mistakes

• SQS Standard for order-dependent events — use SQS FIFO or Kafka instead.
• Kafka without partition key — messages distributed randomly across partitions lose ordering.
• Multiple consumers on a single FIFO queue — only one consumer can maintain strict ordering.
• Not handling out-of-order messages gracefully — even with ordering guarantees, implement idempotency.

Code Examples

// SQS Standard — no order guarantee:
$sqs->sendMessage(['QueueUrl' => $standardQueue, 'MessageBody' => json_encode($event)]);
// OrderCancelled may arrive before OrderPlaced
// Consumer processes cancel before the order exists — state corruption

// Kafka — order guaranteed within partition by entity ID:
$producer->produce(
    partition: $this->partitionForOrder($order->id), // Same order always same partition
    key:       (string) $order->id,
    value:     json_encode($event)
);
// All events for order 42 are in the same partition — strictly ordered

// SQS FIFO with message group:
$sqs->sendMessage([
    'QueueUrl'               => $fifoQueue,
    'MessageBody'            => json_encode($event),
    'MessageGroupId'         => (string) $order->id, // Group per entity
    'MessageDeduplicationId' => $event->id,
]);

References

• ↗ https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html

Tags

Related Terms