← Back to glossary

Message Ordering Guarantees

messaging Intermediate

TL;DR

Message ordering is only guaranteed within a single Kafka partition or RabbitMQ queue — multiple partitions or consumers break FIFO order across the full topic.

Explanation

Kafka: messages within a partition are strictly ordered (by offset). Messages across partitions are not ordered. Partition key determines partition — same key = same partition = ordered. Consumer group with one consumer per partition = ordered processing. Multiple consumers on one partition: not supported (1 consumer per partition max). RabbitMQ: single queue = FIFO within the queue. Multiple consumers on one queue = no ordering. Priority queues alter order. SQS Standard: no order guarantee. SQS FIFO: ordered within a message group, limited throughput. For ordering across entities: use the entity ID as the partition/group key.

Common Misconception

✗ Kafka guarantees global message ordering — it only guarantees order within a partition. For global ordering, use a single partition (kills parallelism).

Why It Matters

Incorrect assumptions about ordering cause processing of 'update' before 'create', or refund before payment — subtle but critical bugs in financial and order systems.

Common Mistakes

Using round-robin partition assignment for order-sensitive messages — breaks sequencing.
Multiple RabbitMQ consumers on an ordered queue — no longer FIFO.
SQS Standard for ordered processing — use FIFO queues.

Code Examples

✗ Vulnerable

// Random partition — order.updated may arrive before order.created:
$producer->produce(RD_KAFKA_PARTITION_UA, 0, $message, null); // Random partition

✓ Fixed

// Same key = same partition = ordered:
$producer->produce(RD_KAFKA_PARTITION_UA, 0, $message, $orderId); // Order by key

// Kafka: max 1 consumer per partition for ordering:
// consumer group size ≤ partition count

References

↗ https://kafka.apache.org/documentation/#intro_topics