Introduction

About Typed Binary Storage

Typed Binary Storage, also known as TBS is a schema-centered serialization format meant for the efficient and performant ser/de of data into a binary form. Designed for minimal if no overhead, TBS should be only memory loads and stores after the ser/de methods are generated. It also implements per-key ser/de without the need to parse first such as in JSON allowing fast mangling such as in Google's FlatBuffers.

Differences from other preexisting ser/de formats

Similar to Avro, TBS encodes only the values of a structure but allows for arbitrary parsing and runtime or compile-time code generation along with less overhead.

It is also similar to FlatBuffers as it implements individual key/value serialization and deserialization without parsing first. Especially useful for mangling data on-the-fly with minimal memory and overhead.

It is different from JSON as it is strongly typed, is in binary form, and is much more performant in all areas by design.

TBS does not allow for RPC calls by default, but these can be implemented by the user. Because of it's simplistic design, TBS should be faster than Protobuf in some cases.

I have not explored the difference from Karmem, but I do know that the AssemblyScript implementation is not nearly as performant as it could be.

If TBS fits your needs, then read on!