3 ms·
If a n+1 version producer sends a message to the message queue with a new optional field, how do the n version consumers have the right schema without relying o
by dtech 3y ago
If a n+1 version producer sends a message to the message queue with a new optional field, how do the n version consumers have the right schema without relying on some external store?
In Protobuf or JSON this is not a problem at all, the new field is ignored. With Avro you cannot read the message.
- nly 3y agoI mean a schema registry solves this problem, and you just put the schema in to the registry before the software is released. A simpler option is to just publish the schema in to the queue periodically. Say every 30 seconds, and then receivers can cache schemas for message types they are interested in.