Magic Enum C++ VS RESTinio

I'm not sure this is quite what you're asking for, but this library has been super helpful to me in the past : https://github.com/Neargye/magic_enum

Also, a shoutout to Magic Enum: https://github.com/Neargye/magic_enum

What does this have to offer over magic_enum?

But it's a hack, and I prefer not to use hacks in production, because of their significant limitations:

You can either write a to string(view) function for your enum or use https://github.com/Neargye/magic_enum

Why reinvent the wheel? magic_enum

Also if you want to convert enum members to string representation I suggest you just use magic_enum instead, much smaller dependency.

Magic Enum provides that.

In my past job, we used https://github.com/Stiffstream/restinio and absolutely loved it. It's not as active but it honestly didn't need much.

Here's a C++ REST framework for you to use too: https://github.com/Stiffstream/restinio

I had a good experience using restinio for a small ASIO HTTP server recently.

It uses restinio https://github.com/Stiffstream/restinio with great success ;)

For networking, pick a networking library. Restinio is a fair choice for HTTP. But, again, feel free to pick others.

You may find this worthwhile: https://github.com/Stiffstream/restinio/issues/101 FWIW, I used Restbed successfully for 3.5 years before switching personal projects to Restino. I've left the job that used Restbed, but I think they are still using it.

Contrary to the direction most people go, I've been writing REST APIs as C++ servers using two different fairly full featured C++ REST frameworks: first using https://github.com/Corvusoft/restbed and more lately using https://github.com/Stiffstream/restinio. These can be peers with any other server, while living on embedded and/or high compute devices for video encode/decode/analysis, deployed ML models, encryption for and remote process communications, model data collection and similar expensive or in-field processing. In both high compute and in-field-no-internet situations creating REST APIs in C++ enables speed and system controls not present in the majority of the mainstream REST frameworks. It's a big world, and here comes ubiquitous high compute...

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