ApiEndpoints VS software-design-patterns

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

I will not discuss the whole process of setting up the project to use these libraries because the source code is for this example is available. For the purpose of this article we will only discuss the Mediator pattern implementation.