ApiEndpoints VS FastEndpoints

I personally prefer the API Endponts project that doesn’t get the love it deserves. It’s really the best of both worlds. It breaks each endpoint up into one file to make it easier to manage and prevents ginormous Controllers.

I personally think it feels "cleaner" when using the controllers instead because they provide more out of the box features. Having one endpoint per file is a nice thing so I'm thinking about using the ApiEndpoints ( https://github.com/ardalis/ApiEndpoints ) package.

You can follow a "controller per endpoint" strategy. One good way to do it is with Steve Smith ApiEndpoints: https://github.com/ardalis/ApiEndpoints

I'm not disputing the benefits of thin controllers but there are other ways to make the controllers thinner. For example, I could use libraries such as ApiEndpoints which allows me to have one handler class per REST endpoint. Basically, MediatR pattern but at the ASP.net level.

The only think I would suggest is to break endpoints into separate files via smth like this https://github.com/ardalis/ApiEndpoints

You really should compare against https://github.com/ardalis/ApiEndpoints

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.