01/09/2026
Adding a field to a message schema is easy, and the harder part is deploying it safely across independently updated producers and consumers.
During rollout, v1 and v2 coexist.
For additive changes, a safer sequence is:
1. Update the consumer first, so it accepts both versions
2. Then update producers to send the new schema
If legacy support becomes long-lived, moving version translation into a compatibility layer can keep it out of core business logic.
More on the trade-offs:
https://curiosum.com/blog/schema-evolution-in-distributed-async-message-passing-systems