Seems to work just fine for StackOverflow... Then again, maybe 560M pageviews per month on 9 web servers isn't nearly enough for your high-level app requirements. They've stayed with ASP.NET MVC since at least v3 back in 2008. Current [1]:
- IDE Visual Studio 2012 & 2013
- Framework Microsoft ASP.NET (version 4.0) on .NET 4.5
- Web Framework ASP.NET MVC 5 with MiniProfiler
- View Engine Razor 3
- Browser Framework jQuery 1.7.1
- Data Access Layer LINQ to SQL and Dapper
- Cache / Additional Data redis 2.8.4 via StackExchange.Redis, with serialization via protobuf-net
- Source Control Git using a self-hosted GitLab instance (previously Mercurial from 2010–2014, Subversion from 2008–2010)
- Compare Tool Beyond Compare 3
Disqus on the other hand (originally based on python/Django) sounds like they've rewritten a lot of their core components into Go. [3] At the end of the day any solid web framework will still need caching thrown in front of it along with high levels of custom tailoring. Both Disqus and SO have done that. Either way the .NET stack has long since proven itself as a capable foundation.
I was referring to its terseness, simplicity, extensibility and the large ecosystem surrounding it.
I said that Django is a better framework for this reason, not your straw man reason.
Scalability is barely an issue. You can horizontally scale both frameworks virtually endlessly if you maintain application statelessness. Dick measuring contests about which company uses what and has the most pageviews do not contribute much to the discussion. Are you going to argue that PHP is a good language because Facebook has a billion users?
I was referring to its terseness, simplicity, extensibility and the large ecosystem surrounding it. I said that Django is a better framework for this reason, not your straw man reason.
You're going to have to link me to the comment where you "referred to" and "said" all of that, because this was all I saw:
Where's the Django for .NET? and Does the same sort of thing, but is not nearly as good.
So maybe I got foolishly got myself into this by bothering to respond to two zero-effort comments. It wasn't a dick measuring contest, the point of the exercise was to examine that a .NET stack (including ASP.NET MVC at its core) can be executed upon with finesse and tuned to efficiency at high operational capacity. Futhermore, other frameworks (i.e. Django) aren't short of their own troubles.
Where's the Django for .NET?