MongoWebApiStarter VS ApiEndpoints

I just started a project with a vertical slice architecture and got some inspiration from this https://github.com/dj-nitehawk/MongoWebApiStarter

this is the one we use for all our new projects.

yes that's what we do. op should just store the sensitive data as environment variables and let the .net config provider read those values during app runtime. you just need to use the double underscore format for naming the variable paths like so: https://github.com/dj-nitehawk/MongoWebApiStarter/blob/a86342d8585d6659dfd677b485f0f22813e9d861/Template/.linux-server-setup/env-variables.txt

if you feel like jumping heard first, have a look at this starter template i have on github. that's what our team uses for all new web api projects.

planning on doing a video tutorial series building a real world app. in the meantime have a look at this starter template project which handles some of that stuff: https://github.com/dj-nitehawk/MongoWebApiStarter

if you're familiar with mongodb, may i recommend an excellent web-api starter template by yours trully ;-)

if mongodb is an option, have a look at this starter template which uses vertical slice architecture.

here's a starter template project that i use.

look into servicestack and vertical slice architecture. check out this dotnet new template where I've implemented both: https://github.com/dj-nitehawk/MongoWebApiStarter

another huge fan of vertical slices here. but I do it without mediatr and use servicestack instead of mvc. here's an example: https://github.com/dj-nitehawk/MongoWebApiStarter

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