[prodbro]

> ASP.NET Core is one of the best web frameworks

I don't think so.

The fact is there are very few dotnet web servers. ASP.NET Core is supported by the owner of the dotnet langage who is also the M of the GAFAM.

There is some place in the ecosystem for other alternatives

[tracker1]

The webserver variability isn't really so wide because the in the box offering since Core has been pretty good, flexible and works for most use cases. And while I really like FastEndpoints a lot over the minimal api stuff, even that is pretty straight forward.

It's not my favorite, it starts slow and I'd rather go up to JS/TS for scripting flexibility or down to Rust for really lightweight performance with fast startups. It's one of the better all-around options though. I'd rather use it over Java every day of the week and there are adapters for most things you'd ever need to communicate with.

[stackskipton]

>The fact is there are very few dotnet web servers.

SRE here, very few because Microsoft is strongly opinionated with ASP.Net and those opinions most sense for VAST majority of their users.

[prodbro]

> those opinions most sense for VAST majority of their users

I have a much more nuanced view.

I think that ASP.Net is the de facto standard for being backed by Microsoft since many years. From the gold time when ASP means IIS to now when Kestrel was cannibalized by Microsoft.

As a developer, working with the most widely used stack guarantees that these choices won’t be questioned in critical situations. I’m not saying Kestrel is bad, but it doesn’t automatically fit every scenario.

- 15 years ago, there were Apache or IIS.

- Then nginx changes the game and kicks their ass

- Then webserver starts being written into script langage for better integration (Ruby, Python), no more CGI and nginx as reverse

- Then node changes the game

- Now : caddy and other alternatives... but still not web server in PHP (troll inside)

I see a pattern to not believe aspnetcore is the only one and the best.