lithium VS asio-grpc

You know what is curious? There is a lib with the same name of your user similar to httplib: https://matt-42.github.io/lithium/

Lithium

If you need an embedded C++ HTTP server then there are plenty of libraries/frameworks (in random order): Crow, RESTinio, Boost.Beast, cpp-httplib, http_backend, Pistache, RestBed, served, proxygen, Simple-Web-Server, drogon, oat++.

#4 https://github.com/matt-42/lithium [Http Server]

Since I can never remember what arguments to pass to protobuf_generate to create Protobuf and gRPC source files, I wrote an article about it. It provides a copy-paste-able code snippet along with an explanation of all arguments that protobuf_generate accepts, how to format it nicely using cmake-format and how to make things easier with asio-grpc.

Asio-grpc makes exactly that possible by providing an Asio execution_context compatible interface to the CompletionQueue. It supports all types of RPCs (including generic ones), completion tokens, cancellation, as well as libunifex sender/receiver (if you want to try out what might become std::execution). The latest release (v1.7.0) also introduced a GrpcStream class for writing Rust/Golang select-style code.

It hasn't been without issue, however. Problems that may lie in official google-maintained libraries are of course present and required design changes, and I was even prompted to write my own bitset library that outperforms the C++ standard's by a factor of 60. Madness. Right?

Or check out the asio-grpc repository directly if you are looking to write asynchronous gRPC services with the features of Boost.Asio like C++20 coroutines, std::futures, stackless coroutines, callbacks and Boost.Coroutines.