Mongoose VS served

I've found myself at this webpage multiple times while trying to minimize the complexity of APIs in my C projects.

My conclusion for now is that C coroutines are something to be left to the implementer. For example: Mongoose (https://github.com/cesanta/mongoose) uses event callbacks to deal with asynchronousness. It is much more pleasant to wrap a library like this in whatever thread/task primitives your system has rather than try to integrate the mythical cross-platform c couroutine.

I remember using mongoose 15 years back. Today i would have considered mongoose(10k+ stars) which is also a mature c/c++ web server[1] if not the licence.

https://github.com/cesanta/mongoose/tree/master/examples

Alternatives at the low to medium level of abstraction include civetweb and mongoose, which have a common ancestor. Both of these appear to be C rather than C++, but seem to be production quality and well-documented. Another C library is cpp-httplib, which is probably too low-level for me.

Since this is only going to be used internally would Mongoose be worth considering?

Here’s an example: https://mongoose.ws/

If you are looking for something simple there is mongoose from cesanta, https://github.com/cesanta/mongoose

We've used this and like it so far: https://github.com/meltwater/served

Just found the link: github

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

So, if you're going that route, you can use one of the many HTTP wrappers around Boost::ASIO or something purpose-built like Pistache or Casablanca.