Discussion: questions about using Asp.net to develop Portals

At present, php accounts for a large proportion of the front-end implementation of large portal websites. I have also engaged in some php websites before, and I like php very much. It has many high-quality open-source projects. Now I want to talk about the implementation of large portal websites. It is inevitable that php will be compared. (Asp.net uses c # As the implementation language by default)

In my personal interests, I prefer C #. From a Language Perspective, php is an explanatory language, which is slower than C. However, the language for building a large system is just a small development. More are the background web containers and OS. The configuration of an asp.net system is as follows:

C #, iis, windows server 2008, SQL server/orcal/mysql)

Using iis and window server 2008 is the root cause of my opinion that asp.net is not suitable for cooperation with large portals-it is not open-source, customizable, or optimized. To implement a large portal, its traffic and load are of a very large order of magnitude. db, io, cache, and concurrency are all issues that need to be solved, I personally think that there is limited space for expansion and Optimization on non-open source iis and window server 2008, which effectively solves the problems. Especially when there are too many servers, the cost of software will rise sharply, which also needs to be considered. Therefore, I think the current asp.net is not suitable for developing large portals. Its characteristics should only be applicable to enterprise system application development. If the performance and expansion of asp.net in linux and apache can be very good that day, I believe it will be even better (Mono I think is still immature ).

Of course there are many other problems, such as the page is not suitable for seo and so on, but these can be solved, the core is its web container, and OS.