We have a distributed system with multiple environments and have integrated a Schema Registry with some of our services. So far, we’ve created some tooling to aid in the migration of our schemas.

We have a distributed system with multiple environments and have integrated a Schema Registry with some of our services. So far, we’ve created some tooling to aid in the migration of our schemas.

I have an application in which am using Kafka with schema registry to produce messages.I have a topic called plans , in which there are fields like id,name,type etc.,. Now there are deiffrent fields which are having a value only for certain type of plans. Example am having fields such as ‘time’ ,`duration’ for only one type of plan . And there are different fields which are common for 2 or 3 types of plans . The current AVRO schema is linear , so if i have to add a new type of plan , again i will add 2 or 3 fields which are having a value directly in to schema . This is causing the fields to grow horizontally at consumer end . Is there any way using which i can come up with a scalable AVRO schema which may of some nested type , so that the fields won’t grow horizontally and which is not complex to use at consumer end also .

Suppose I have a number of avro schema definitions: (i) Event1, (ii) Event2, (iii) EventWrapper.