For small and medium-sized enterprises to establish their own web site, the external display of their own page is the most common thing. The most popular setting up of WWW service tools is Apache and IIS. So what's the difference between them? What is the best tool for us? Today we will discuss this issue.
first, free and charge of the dispute:
Although many users use IIS to build a Web site, they are components that are integrated into the Windows operating system. However, if you want to use IIS legitimately, you will need to purchase a genuine Windows operating system.
Against Apache, he's completely free. It is free to download and use without paying any fees.
Conclusion--apache is free, and the former takes advantage of the charge of IIS.
second, Stability:
The next thing to compare is stability, the WWW service to run normally, a website also needs 24 hours a day, seven days a week for the public to open. So stability is the focus of IIS and Apache comparisons.
IIS often has 500 errors in actual use, and sometimes there are unexplained signs of suspended animation. Users need to restart the IIS service periodically to ensure that the site is normal.
Apache is more complex to configure than IIS, but it can work long term once it is set up. Large Web sites use Apache as their own WWW service delivery tool. All of Apache's configurations are saved in the configuration file, and are used exactly as the information is recorded in the configuration file. There will be no unexplained suspended animation in general.
Tip: Using IIS under the WINDOWS2003 system is better than using Apache performance.
Conclusion--apache is stable, and IIS is sometimes suspended in death, which takes precedence.
third, the expansion of:
Extensibility refers to whether the WWW service delivery tool can be applied to a variety of situations, a variety of network conditions, a variety of operating systems.
IIS can only be used under Microsoft's Windows operating system, leaving windows to accomplish nothing. Cannot be ported to other types of operating systems.
Apache is versatile, not just for windows, but for a variety of operating systems such as Unix,linux and FreeBSD. And the configuration steps of different operating systems are basically similar, the portability is very high.
Conclusion--iis can only run under Windows, with a wide range of Apache applications. Apache wins.
Four, security:
Often see So-and-so site by hackers or certain sites are illegal users upload the virus message, for others to provide services to the site, security is the most important. If a website has no guarantee of its own security, who would like to browse and use it.
Early IIS has a large security problem, and if you use the default settings, hackers can easily swoop in. But in IIS6, Microsoft has made significant security improvements. As long as you ensure that the operating system patch updates in time, you can increase the safety factor of the site as possible. In particular, IIS6 and the. NET platform rely on each other, making security almost perfect.
Apache has been doing a good job in security, because many users are in Linux under the use of Apache, so the characteristics of the operating system so that the Linux under the inherent umbrella of Apache, security is naturally not said.
Conclusion the previous version of--IIS6 has security implications, and IIS6 is as safe and reliable as Apache. IIS6 a tie with Apache.
v. Openness:
So-called openness is whether the source code of the program is open, and it is well known that IIS is part of the Windows system, so his source is not open. And Apache is different, the earliest he is for Unix-like system services, so completely open to the source code. Anyone can analyze his code, discover the vulnerabilities, and post patches to remedy the vulnerability.
Because of this openness of Apache, it also makes its security greatly improved.
Conclusion--iis not open code, Apache open source code. The latter won.
Vi. Difficulty and accessibility:
The ease with which a tool is used directly affects the number of users, especially Web publishing tools. After all, many companies want to have their own web site, but do not want to hire a high-paying network administrator to maintain. Therefore, it is necessary to find a relatively easy tool to build their own site.
IIS is simple to open, and it's easy to get IIS to work and publish Web sites externally. However, administrators are prone to error configuration and misoperation problems. But generally speaking, IIS is very easy to learn, but it is very difficult to learn him well.
Apache is more difficult to use than IIS, and it requires people with a certain computer and network base to use it. His configuration is not graphical, we need to edit the configuration file to achieve. But only from the Apache settings, as long as we strictly follow the Help file to set the parameters of the word is not difficult.
Conclusion--iis is easy to install but difficult to master, Apache installation is relatively difficult, it is not easy to master. IIS has a slight advantage.
Seven, Programming:
In order to make the page more colorful, more beautiful, interactive better, master for us to develop a variety of components and controls, then these controls in the IIS or Apache under the normal operation?
The MoD rewrite in Apache is very powerful, and the rewrite of the ISAPI in IIS needs to be specially developed, which is not possible for beginners in general. Apache can use the Subversion WebDev as well as the. htaccess feature, and you can also use Forcetype. In addition, IIS to FASTCGI support is not very good, so some CGI, PHP program to run slowly, far less than Apache.
Conclusion-use different components in different environments, because choosing IIS or Apache is determined by the working environment.
Viii. Support for language aspects:
Because of the current establishment of the Web site and forum language is diverse, such as asp,php,jsp and other languages. So do IIS and Apache support them?
IIS is stable for ASP, especially. NET, but it is more cumbersome for PHP and JSP. PHP needs to be configured repeatedly to support the windows2003. Apache is good at supporting several of the above mentioned languages, running asp,php,jsp without any problems.
Conclusion--apache support Language is more, IIS support PHP and JSP a bit cumbersome, need to go through a certain configuration. Apache wins.
ix. Treatment aspects:
When it comes to treatment, many readers may wonder, how can IIS and Apache still have treatment? In fact, we are here to discuss the treatment of network administrators. An IIS network administrator and an Apache network administrator, their salaries are not the same.
The biggest advantage of Apache is that there are many configuration parameters, if you want to master Apache needs a high level. So the same level of network administrator will be better than the Apache to the IIS treatment.
Conclusion-more money is the only standard to win, Apache is dominant.
Summary:
In fact, we are here today to argue that the good of IIS or Apache is not very significant, the comparison of this article is just for those wandering in the network administrator intersection, do not know which tools to learn which tool to build the site's readers a little reference. Only if you have a general understanding of IIS and Apache can you plan for your future.
Overall, Apache has the advantage of being the most diverse, widely supported, relatively stable, and extensible in a wide range of open source WWW service delivery tools. However, because of scalability, performance is certainly not too high, only to maintain a moderate level. And IIS6 is still very powerful in handling connection and event performance, surpassing Apache. In addition, security IIS6 also has a qualitative leap, to make up for the previous IIS loopholes in the sky. If your company's network environment is not responsible, do not involve too much development, suggest still use IIS6. Of course, if it is built on the WWW development and debugging or use Apache more smoothly.
