Avro never gets any love, which is a real shame given its extremely powerful schema resolution rules[0] You don't have to worry about maintaining numeric field

Avro never gets any love, which is a real shame given its extremely powerful schema resolution rules[0] You don't have to worry about maintaining numeric field tags, can remove fields, can make previously required fields optional (by promoting them to unions with null), or even change their type (by promoting them to unions of <old type> and <new type>) You need to pass your schema around with your data somehow, but there's a file format specified for that, and you can still just dump to JSON if you can't be bothered. The schemas are specified in JSON too... which in my view makes it more robust than the JSON + JSON-Schema combo [0] https://avro.apache.org/docs/current/spec.html#Schema+Resolution https://avro.apache.org/docs/current/spec.html#Schema+Resolu...