The debate about J2EE and .NET has been conducted for a long time, it is estimated that it will continue. I am also from writing procedures, for J2EE
And .Net has a certain understanding. I feel that no matter whether J2EE is selected, it is summarized from three aspects: demand,
This, scalability. [Demand, Cost]: What is the degree of actual demand? This must be clear. Don't actually
The number of visitors will not exceed 100 people, but also on WebSphere, or expensive products such as WebLogic. Tomcat, IIS
The class is far enough. Don't actually have the amount of data to be up and down, and the Database, MS SQL Server, and MS SQL Server.
It is already very wasteful, and even Access can be fully satisfied. In fact, just want to be a corporate site, mainly propaganda, no
Large service, but also to call J2EE, what is the like. In fact, it is not necessary, small applications such as ASP and PHP are far enough, and the cost is also
A lot of bottom. In general, it is to clear your actual demand, do not take high-fire guns. [Scalability]: This is also
It is a very important aspect. It is possible to clearly expect the development of demand, perhaps the current demand is not very large, but its development space,
The rest is very large. Then take into account the problem of the future upgrade. In this case, the initial architecture design is large, avoiding the limitations of future system upgrades. Personally think --- Small Applications: (Windows) IIS ASP Access or (Liunx) Apache PHP
(JSP) MySQL Medium Application:: (Windows) IIS ASP (C #) MS SQL Server or (Liunx) Apache PHP
(JSP servlet java bean) mysql large application: That don't say it. Ha ha.
