Apache Thrift VS Cap'n Proto

Thus, we released Baseplate.py v2.1 with deadline propagation. Each request between Baseplate services has an associated THeader, which includes relevant information for Baseplate to fulfill its functionality, such as tracing request timings. We added a “Deadline-Budget” field to this header that propagates the remaining timeout so that information is available to the following request, and this timeout continues to get updated with every new request made. With this update, we save production costs by allowing resources to work on requests awaiting a response, and gain overall improved latency.

Here’s an example of the Thrift changelog. Knock yourself out. Or you can get your sense of productivity by actually doing something of value.

The biggest addition is native async reading via futures::AsyncRead and futures::AsyncSeek, which required a lot of (to be merged) changes upstream (changes to thrift rust compiler and parquet-format-rs). I placed those changes on a temporary crate until things are released there.

We were sharing instances of a Thrift TDeserializer across threads. We knew TProtocol was not thread-safe, but the TDeserializer constructor accepts a TProtocolFactory, so we naively assumed the deserialize method would use that to create a new instance of TProtocol for each invocation, but unfortunately, the TDeserializer constructor immediately creates TProtocol and stores it in a member variable, so TDeserializer is not actually thread-safe.

Hi! Thanks for taking a look. TBH a just did it yesterday night so the lib is more than immature, so you are right when you say it is not optimized. I'll try to spare time to improve it and offer those benchmarks. However I dare to say that it may produce faster and lighter results than standard 'encoding/json'. Protobuf takes advantage of code generation so I would say that would produce higher compresion ratio. And definitely worse that https://capnproto.org/

A coworker added coroutines to KJ [1] so for our purposes it’s “made it”. It’ll be more broadly useful obviously with library support in the standard. I think that’s targeted for c++23

[1] https://github.com/capnproto/capnproto/blob/master/kjdoc/tou...

Or use Cap'n Proto [1] and eliminate all serialization costs.

[1] https://capnproto.org/

Cap’n Proto — serialization library

I guess an example would be along the lines of protobufs, e.g. Cap’n Proto

https://capnproto.org/

(which I have never used but really enjoy just for its charming website design alone)

how does it compare against cap'n proto?

Another interesting, similar and older project is Cap'n Proto.

You want Cap'n Proto, the successor to Protobuf.