When producers and consumers evolve independently, a consumer needs the writer schema to interpret a serialized message. With Avro and a schema registry, the producer includes a registry-assigned schema identifier in the message header. The consumer uses it to retrieve the writer schema, then resolves it against its own reader schema. section 8.1.6
Resolution can fill fields absent from the writer message with defaults in the reader schema. A registry can also enforce compatibility when schemas are registered and expose checks for build tools. This supports schema evolution and independent deployment while retaining compact binary encoding; the trade-off is requiring additional tooling. section 8.1.6
