AspNetCore.Proxy VS ABP

By setting up your backend as a proxy to another API, you're setting up extra code: your front end makes a request to your back end, and your back end makes an almost identical request to another API, which means more code to maintain and more unit tests to write. A lot of the code duplication goes away if you use a package like AspNetCore.Proxy to do most of the heavy lifting with implementing a proxy.

In conclusion, ABP Suite is a game-changer in the realm of application development. Its modular design (comes from ABP Framework), powerful code generation, and support for modern frontend frameworks make it a go-to choice for developers looking to build scalable and feature-rich applications. Whether you are working on a small project or a large enterprise application, ABP Suite provides the tools you need to succeed in your development endeavors.

We use something like this at work: https://abp.io/

Take a look at abp.io. The framework is free and there is also a commercial version. It supports Blazor Server and WebAssembly UI layer.

Even better, try this version: https://github.com/abpframework/eShopOnAbp which is eShop on the ABP framework which I highly recommend.

We're using ABP and TinyMVVM along with the CommunityToolkit.Mvvm, working nicely.

Best i can think of is https://abp.io/

See the abp.io source code and document. Excellent documentation and well structured code.

I'd like to suggest ABP. Follow the getting started tutorial. They also blog about DDD things and offer some additional info and articles about it on the site and in the walkthrough.