Welcome to the discussion on ASP.net's large portal website.

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 ).

You are welcome to make a lot of comments.

To sum up, Asp.net can certainly be used for large-scale applications. If you do not select Asp.net, you need to consider various factors, including software costs, human resources costs, and familiarity with technology. We should pay more attention to how to avoid problems encountered when building large websites. This requires in-depth study and discussion. The language selection can be based on the degree of familiarity we use. Thank you! If you have any questions about solutions for building large websites, please share them with us. Thank you.

Below is a link to the article on the architecture of two large websites:

Http://www.blogjava.net/BlueDavy/archive/2008/09/03/226749.html (evolution of large website architecture and Knowledge System)

Http://blog.zhangjianfeng.com/article/743 (from livejournal Background Development to view large-scale website performance optimization methods)