I'm writing a multitenant (serving different domains)hosted CMS with mvc 4 (will update dlls to mvc5 and code to async soon ). if your architecture is good and you know how to do caching you will be good to go for many users to come :) (asuming you have nginx in front iis is simply not designed for that purpose)
I have to disagree here... IIS does extremely well with static resources, and tends to tie well into the file system caching. If you don't need to go through so much as say HAProxy or Varnish in front of IIS, I wouldn't really bother with nginx, unless you use nginx as a reverse proxy to several IIS servers.
.Net as an application stack has some weight to it, so fronting several .Net servers with nginx makes sense. Just wanting to point out that putting a reverse proxy in front of your application before, or unless you need to and already have the infrastructure in place, don't do it. And, again IIS does very well with static resources, and Application Request Routing (ARR, which is an IIS reverse proxy system) does really well also. I've used ARR a number of times to front node.js based apps (API services) with IIS.
Don't get me wrong, if you have nginx servers, and want to reverse-proxy for load balancing reasons, go for it. If you are simply wanting to improve serving static resources, IIS does very well here. Mixed loads are what tends to drag things down.
That little sub-thread was...ok. Informative, but a bit low on the drama.
Still no dark clouds over that Visual Studio icon. Microsoft might be "dead", but the "Developers Developers Developers" warcry echoes on, and the cushy jobs and well-paid freelancing gigs will be there for many years to come!
That's funny... where I work now, most new development is being done in node.js, with a migration strategy to get most of our backend (for the apps I work with) onto node.js by the end of the year (from .Net) ...
I've been pushing for node.js (as a JS, and node fan) for the better part of the past 5 years now (since node started)... So, definitely not tied to MS, but do make my living on supporting their tech stack, for the time being.
I just wanted to point out that simply fronting IIS with nginx is a flawed idea, unless you have reason to do so, and/or already have the nginx infrastructure in place.
