C++ REST SDK VS ProxyKit

My favourite was Microsoft's cpprestsdk, but for some reason now is in maintenance mode, I don't know why, so it's hard to suggest it for new projects. A nice alternative is restc-cpp, that's has a good high-level interface, if this is what you want.

CppRestSDK is deprecated.

https://github.com/microsoft/cpprestsdk (concerned about being maintenance mode -> production?)

While it's not based on Boost Asio or Beast, Microsoft maintains a SDK for developing REST api's using C++, aptly named the C++ REST SDK. Here you can find the Github page. It pretty much covers everything you'd come to expect from a modern webserver package. It does come with a steep learning curve however.

I never thought I'd laud microsoft on open source software but this has certainly made my life easier... I mean come on, MIT licensed and everything...

https://github.com/microsoft/cpprestsdk

Assuming you want to make a REST API check this out: https://github.com/Microsoft/cpprestsdk

>But is it truly practical to use in 'higher-abstraction' apps like web or mobile?

Yes absolutely. Once you become familiar with the language the barrier is not that high. Familiarity trumps everything else.

That said, since i am not a Web/mobile developer i had collected some resources to help me learn how to use C++ for Web/Mobile apps, you may find it useful;

https://levelup.gitconnected.com/cross-platform-mobile-and-w...

https://github.com/Microsoft/cpprestsdk

https://medium.com/@ivan.mejia/modern-c-micro-service-implem...

I was starting a project that needs to read data with rest API and I'd like to use cpprestsdk from Microsoft. But it's readme says that's in maintenance mode and it's not recommended for new projects... I'd like to know why it's in maintenance mode, and if it will be abandoned. Also, if there's some equivalent library for cpp, instead of creating the business logic from scratch, i.e. with boost::beast.

Worth noting that YARP (or as someone has eloquently described it as PRAY) here was another Microsoft project which basically killed a previous open source project which did the same thing:

https://github.com/proxykit/ProxyKit

This actually feels like one of the instances that PeachPie with a combination of ProxyKit or YARP would be handy.

You could setup a proxy with ProxyKit in you WebHost. Your blazor app will send requests to, say http://webhost:5000/api/endpoint. The host will then forward the request to http://webapi:3000/endpoint (or whatever). You'll have to setup some kind of JWT authentication where the WebHost generates a JWT on login and saves it in the cookie. Good thing here is, the cookie really only contains some id the server uses to look up the actual contents of the cookie. Only the cookie gets returned to the browser (blazor app). On each api request, the webhost will fetch the token out of the server-side cookie and append it to the Authorization header. The webapi will validate the token and return the response that will be proxied back to your front-end.