Pistache VS Oat++

A coworker at my last job used pistache.io as a web back-end framework for C++ to good effect. I have no idea if it's the best, or even good, but I know that he made a project with it that I was calling into (I was building the front-end) and it worked.

There are some C++ API frameworks like Pistache or Restbed (full list here) to get started. If I should be 100% honest, I don't think C++ is worth for APIs as we have easier solutions with the same performance nowadays (like Go and Rust), but I think we should try everything, right?

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++.

Oat++(OatPP) is a lightweight C++ Web framework. Out of the box, it provides REST API with built-in JSON serialization/deserialization features, which could be interfaced with your DTOs.

mkdir temp && cd temp git clone https://github.com/oatpp/oatpp.git

I looked at oatpp and drogon, which are both great, but feel too high-level for my purposes. I tried drogon and got something working, but it feels like too much for my requirements, as in particular I'd like to slot in my choice of Json and message-body handling. C.f. the simple approach in Crow, which I easily understand and build on.

With the right libraries, C++ could be a good fit for applications that want to expose a fast web API to things that need lots of compute (simulators, for instance) or I/O (interactive editing of large datasets). Projects like Oat++ and Crow give me hope that we might see such an ecosystem develop.

Lots of other options have been mentioned, but I'll throw Oat++ into the mix. I used it for this purpose and it was reasonably painless.

https://github.com/oatpp/oatpp +WASM ;)

cd "some/temp/path/for/repositories" git clone https://github.com/oatpp/oatpp.git cd oatpp mkdir build && cd build cmake .. (sudo) make install