Persistent Collection VS Apache Avro

So does Java! Also, kotlinx.collections is still not stable and I don't think they are intending to make it so any time soon.

> If you are using containers, always, always, always use immutable containers from Google Guava unless you have an exceptionally good reason.

I actually prefer pcollections: https://github.com/hrldcpr/pcollections

AtomicReference + immutable data types is a really nice way to program in Java, and is basically the way most Clojure programs are written.

You might consider persistent collections instead of immutable collections, I believe it is more optimized https://github.com/hrldcpr/pcollections

Apache AVRO [1] is one but it has been largely replaced by Parquet [2] which is a hybrid row/columnar format

[1] https://avro.apache.org/

The most common format for describing schema in this scenario is Apache Avro.

I am testing a new schema registry which loads and retrieves different kinds of avro schemas. In the process of testing, I need to create a bunch of different types of avro schemas. As it involves a lot of permutations, I decided to create the schema programmatically.I am using the apache avro SchemaBuilder to do so.

Other serialization alternatives have a schema validation option: e.g., Avro, Kryo and Protocol Buffers. Interestingly enough, gRPC uses Protobuf to offer RPC across distributed components:

Apache Avro is a data serialization system, for more information visit Apache Avro

Once things like JSON became more popular Apache Avro appeared. You can define Avro files which can then be generated into Python, Java C, Ruby, etc.. classes.

Avro, a data serialization system based on JSON schemas.

Supporting multiple versions of an event schema is a solved problem. Apache Avro with a published schema hash in a message header is one solution.

https://avro.apache.org/