nachricht
A self-describing data interchange format (by yasammez)
nachricht | rust-serialization-benchmarks | |
---|---|---|
4 | 1 | |
74 | 89 | |
- | - | |
0.0 | 0.0 | |
about 2 years ago | over 3 years ago | |
Rust | Rust | |
MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nachricht
Posts with mentions or reviews of nachricht.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-09.
-
I made a blazing fast and small new data serialization format called "DLHN" in Rust.
Asking because I am interested in serialization myself (shameless self-plug: https://github.com/yasammez/nachricht )
- rkyv is faster than {bincode, capnp, cbor, flatbuffers, postcard, prost, serde_json}
- Introducing nachricht: a self-describing binary data-interchange format that uses backreferences to save bytes on wire
- Nachricht – A self-describing data interchange format
rust-serialization-benchmarks
Posts with mentions or reviews of rust-serialization-benchmarks.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-11.
-
rkyv is faster than {bincode, capnp, cbor, flatbuffers, postcard, prost, serde_json}
Right, great question. I referenced one benchmark in the post that separated the populate and serialize steps. This is a bit of a fuzzy patch for the methodology: what should count as serialization? I think there could be arguments either way:
What are some alternatives?
When comparing nachricht and rust-serialization-benchmarks you can also consider the following projects:
bytecheck - Memory validation framework for Rust
rkyv - Zero-copy deserialization framework for Rust
rust_serialization_benchmark - Benchmarks for rust serialization frameworks
dlhn - DLHN implementation for Rust
tree-buf - An experimental serialization system written in Rust
NoProto - Flexible, Fast & Compact Serialization with RPC
nachricht vs bytecheck
rust-serialization-benchmarks vs rkyv
nachricht vs rkyv
rust-serialization-benchmarks vs rust_serialization_benchmark
nachricht vs dlhn
rust-serialization-benchmarks vs bytecheck
nachricht vs rust_serialization_benchmark
rust-serialization-benchmarks vs tree-buf
nachricht vs tree-buf
nachricht vs NoProto