LeapSerial
SBE
| LeapSerial | SBE | |
|---|---|---|
| - | 7 | |
| 17 | 3,023 | |
| - | 0.2% | |
| 0.0 | 8.7 | |
| about 6 years ago | 2 days ago | |
| C++ | Java | |
| Apache License 2.0 | Apache License 2.0 |
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.
LeapSerial
We haven't tracked posts mentioning LeapSerial yet.
Tracking mentions began in Dec 2020.
SBE
- Simple Binary Encoding (SBE) – High Performance Message Codec
- Simple Binary Encoding (SBE)
-
Possibly stupid question, is java the right language for low latency and high throughput web servers?
I was about to suggest Chronicle, but it looks like they have gone closed-source. The older version is still interesting to look through though. Aeron / Disruptor / SBE are good projects for inspiration as well.
-
GitHub - realtimetech-solution/opack: Fast object or data serialize and deserialize library
Could you evaluate how it compares with SBE?
-
Simple Binary Encoding (SBE) now supports Rust
The Simple Binary Encoding (SBE) project now includes support for generating Rust code. Generated code produced does not use unsafe and has no dependencies on any other crates.
-
I made an NBT-based data format, but a little more general purpose
SBE
-
Parsing Protobuf at 2+GB/S: How I Learned to Love Tail Calls in C
Consider a valid protobuf message with such a field. If you can locate the field value bytes, you can write a new value to the same location without breaking the message. It's obviously possible to the same with the varint type too, as long as you don't change the number of bytes - not so practical, but useful for enum field which has a limited set of useful values (usually less than 128).
Pregenerating protobuf messages you want to send and then modifying the bytes in-place before sending is going to give you a nice performance boost over "normal" protobuf serialization. It can be useful if you need to be protobuf compatible, but it's obviously better to use something like SBE - https://github.com/real-logic/simple-binary-encoding
What are some alternatives?
Nameof C++ - Nameof operator for modern C++, simply obtain the name of a variable, type, function, macro, and enum
Protobuf - Protocol Buffers - Google's data interchange format
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
Boost.Serialization - Boost.org serialization module
Apache Avro - Apache Avro is a data serialization system.
MessagePack - MessagePack implementation for C and C++ / msgpack.org[C/C++]
cppcodec - Header-only C++11 library to encode/decode base64, base64url, base32, base32hex and hex (a.k.a. base16) as specified in RFC 4648, plus Crockford's base32. MIT licensed with consistent, flexible API.
The IOD Library - Meta programming utilities for C++14. Merged in matt-42/lithium
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library