NoProto VS Apache Avro

You can easily use allocation and allocation dependent data types with the ‘alloc’ crate. Everything in the alloc crate will honor a global allocator set by the host application. I built a no_std crate with allocation, if you’d like to check it out for examples: https://github.com/only-cliches/NoProto

Looks awesome! Do you mind if I add this library to my benchmarks? https://github.com/only-cliches/NoProto#benchmarks

There is now: https://github.com/only-cliches/NoProto/issues/10

I'm trying to add your library to my benchmarks and it's seg faulting. It's possible I'm doing things wrong, but once I reach this method the benchmark fails and segfaults.

Benchmark Source

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/