3 ms·
I started a recent project with gRPC but wound up moving to fbthrift after having a bad time with the C++ async server story. Overall I’d like to be using gRPC
by benreesman 6y ago
I started a recent project with gRPC but wound up moving to fbthrift after having a bad time with the C++ async server story. Overall I’d like to be using gRPC because the fbthrift documentation is weak, but thread-per-request is a non-starter for some use cases. From the gRPC source it looks like they’ve got plans to do something about it but it seems a ways off.
- jeffbee 6y agoWhat specifically was your problem with grpc c++ async? I'm using async C++ with one CQ per core and it seems to more or less work.
- benreesman 6y agoIt was not obvious to me how to support a large number of methods without a bunch of error-prone boilerplate. It seemed very low-level, which is fine if you have a small number of interactions but it started getting out of hand quickly and fbthrift does this neatly out of the box.
- apta 6y agoAre you bound to C++ for the implementation?
- benreesman 6y agoDebatable, latency matters. It’s possible that Rust or a well-tuned JVM could be an alternative, but C++ is a sure thing and schedule matters too.
- apta 6y agoWhat's the domain? Financial, or something else out of curiosity?
- benreesman 6y agoFinancial.