Boost.Asio VS Oat++

Indeed looks like it, strand_executor_service.hpp is using a Mutex internally (otherwise it wouldn't make sense to me).

as a side note, Asio is also released as an independent library without the boost stuff https://think-async.com/Asio/

Now that vinniefalco is going to kill off the asio standalone (see deprecate standalone ) and only support boost what would people then recommend to switch over to.

The ASIO framework can be found at https://think-async.com/Asio/ and the relevant license for its use is included in the GitHub repository in the Vendor/licenses directory.

The library is found at https://think-async.com/Asio/.

Asio Extracted from the much bigger Boost C++ library, it's apparently a really good networking library. As a bonus it also handles async / threads. Here's a really good video tutorial by OneLoneCoder

Yes: https://github.com/chriskohlhoff/asio/blob/master/asio/include/asio/coroutine.hpp

Here's the main contributor to Asio. I looked at Asio's repository and this was the first guy.

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

Maybe use something like https://oatpp.io to create a REST API: C++ in the backend with this library to create a REST server, and the JavaScript/TypeScript frontend to ask for the information.

I've used OATPP ( https://github.com/oatpp/oatpp ) which worked nicely for setting up simple rest interfaces. Supports things like swagger & websockets out of the box. It's also on Conan which is nice if you use cmake. I can't speak to it's performance but it has about a 1mb binary size footprint.