Handling schema drifts
A schema drift refers to the changes in schema over time due to changes happening in the event sources. This could be due to newer columns or fields getting older, columns getting deleted, and more.
Handling schema drifts using Event Hubs
If an event publisher needs to share schema details with the consumer, they have to serialize the schema along with the data, using formats such as Apache Avro, and send it across Event Hubs. Here, the schema has to be sent with every event, which is not a very efficient approach.
If you are dealing with statically defined schemas on the consumer side, any schema changes on the producer side would spell trouble.
Event Hubs provides a feature called Azure Schema Registry to handle schema evolution and schema drift. It provides a central repository to share the schemas between event publishers and consumers. Let's examine how to create and use Azure Schema Registry.
