When the job service produces the JobStatus change events, it was noted that events might be delivered via different partitions when we work with kafka.

This might produce that events arrives not necessarily in the order they was produced. Generating unwanted information updates.

For that purpose, we must be sure to use the event "key" proposed by kafka to ensure events for the same job, goes via the same partition, and thus, the delivery order is preserved.