The current ASP.NET stack is exactly what you're describing: hundreds of modules loaded by default and it takes lots of effort (and sometimes impossible) to not load it all if you dont need it. It's still pretty fast though.
.NET Core is the other way around and you load everything you need. If that's 2 or 200 modules, that's fine. This model combined with the lightweight hosting is what allows for the million req/sec benchmarks now.
200 modules isn't much at all. Servers today are also very fast, so this is not going to be a problem. What exactly are you concerned about?
.NET Core is the other way around and you load everything you need. If that's 2 or 200 modules, that's fine. This model combined with the lightweight hosting is what allows for the million req/sec benchmarks now.
200 modules isn't much at all. Servers today are also very fast, so this is not going to be a problem. What exactly are you concerned about?