A key connects related events to a partition. With the same partition count and compatible partitioning, records with the same serialized key go to the same partition. That gives a useful order for one order or account, while unrelated keys can run in parallel. Kafka does not promise a single order across partitions. This model uses the Java client Murmur2 keyed calculation for UTF-8 strings. Unkeyed routing is simplified to a deterministic round-robin rule rather than real sticky batches. Send the requested lifecycle events in order and inspect their keys as well as their offsets. An accidentally different key can quietly break the business sequence.
Inspect the topics, partition logs and group offsets before changing the cluster.