FastEndpoints VS FastEndpoints

In a recent podcast episode I recorded with Nick Chapsas, we discussed both Minimal API and Mediatr (due to be published on the 1st April). He mentioned a library I hadn't heard of before called Fast Endpoints, which is yet another option. So many different ways to skin a cat. I haven't used Carter, but did use Nancy back in the day.

There's also Fast Endpoints as another way of doing a similar concept (This has API design issues imo, but the concept is solid). It ends up being similar to how a lot of people use MediatR, it's just instead of using controllers you use MapXXX to call MediatR. This just allows people to cut out the MVC overhead.

i believe i've built such a thing. or at least something close to that ;-)

awesome! page looks a bit empty. maybe my rest api framework belongs there too as it's an implementation of REPR pattern https://github.com/dj-nitehawk/FastEndpoints

that's why integration/functional testing with WebApplicationFactory is the way to go.

Bonus Time! In addition to the Microsoft-supported methods above, many community frameworks exist for building APIs with .NET. FastEndpoints is an option I found recently that seems very promising. With performance benchmarks that put them on par with Minimal API, they are firmly ahead of Controller-based APIs.

Have you had a look at FastEndpoints yet? Any thoughts?

And yet, all Microsoft's demos for the upcoming changes for Blazor in .NET 8 (like SSR) has been a public facing recipe site (e.g. https://www.youtube.com/watch?v=QD2-DwuOfKM). I'd say this is a very similar use case as the Microsoft Store.

I love .NET and ASP.NET Core, but I use it purely for backend. And even there, I use 3rd party libraries like Fast Endpoints (https://fast-endpoints.com/). Microsoft keeps bringing in new technologies and effectively abandoning the ones that fall out of favour (look at the progression from MVC -> Razor Pages -> Blazor). I do not blame the Microsoft Store team for not trusting the .NET team to not simply abandon Blazor as well somewhere down the line and instead opt for other technologies for the front-end.

I also find a very similar framework in .NET "Fast Endpoints"

I gave it a go and I was impressed how easy and fast it was to set it all up. Since I'm not a big fan of REPR pattern almost all my projects are using CQRS pattern with a help of MediatR ](https://github.com/jbogard/MediatR) I immediately started going over something similar that Fast Endpoints offer which is a command bus.

Ive personally been using FastEndpoints which is a community built thing on top of minimal apis - https://fast-endpoints.com/

I've just started to use a similar thing, and it's so much better than controllers - https://fast-endpoints.com/

Sort of minimal but check out FastEndpoint. https://fast-endpoints.com/