Comparison between the Iis,apache,tomcat of Web servers

The difference between iis-apache-tomcat
The difference between IIS and Tomcat

IIS is the Web server for Microsoft Corporation. The main support ASP language environment.
Tomcat is the standard implementation of Java Servlet 2.2 and JavaServer Pages 1.1 technology and is a SJP language environment container developed under the Apache license, which is strictly not a Web server, but an Apache service adapter.
Tomcat's primary task is not to Web services, but to support the JSP language environment.
IIS is also a Web server that supports ASP locales

The difference between Apache and Tomcat

Apache is a Web server environment program enabled he can use as a Web server but only supports static web pages. But asp,php,cgi,jsp and other dynamic Web pages will not work.
If you want to run JSP in the Apache environment, you need an interpreter to execute the JSP Web page, and this JSP interpreter is Tomcat, why do you want the JDK? Because the JSP needs to connect to the database, the JDK to provide a connection to the database drive, so to run the JSP Web server platform needs APACHE+TOMCAT+JDK Consolidation benefits: If the client is requesting a static page, Then only the Apache server responds to the request if the client requests a dynamic page, then the Tomcat server responds to the request because the JSP is the server-side interpretation code, so consolidation can reduce the service overhead of Tomcat.
Apache is a Web server, Tomcat is an application (Java) server, it is just a servlet (JSP also translated into a servlet) container, can be considered an Apache extension.
Apache: Ordinary server, itself only supports HTML that is ordinary Web page, it is an HTML container, functions like IIS
Tomcat: Explains the Java program (Jsp,serverlet), which is a jsp/servlet container for publishing JSP and Java
Apache is a truck that can pack something like HTML. But the water must be filled with containers (buckets), and Tomcat is a bucket (a water like Java), and the bucket can be kept out of the truck.

The difference between IIS and Apache

For small and medium-sized enterprises to establish their own website, the external display of their own page is the most common thing. At present, the most popular set up WWW service tools will belong to Apache and IIS. So what's the difference between them? which tool is best for us? Let's talk about the problem today.

One, free and charge of the dispute:

Although many users use IIS to build Web sites, they are components that are integrated into the Windows operating system. However, to legally use IIS, you will need to purchase a genuine Windows operating system.

In view of Apache, he is completely free. It is free to download and use without paying any fees.

Conclusion--apache free, IIS charges, the former accounted for excellent.

Second, Stability:

The next thing to compare is stability, WWW service to work at any time normal, a website also need 24 hours a day, seven days a week for the public open. So stability is the focus of comparison between IIS and Apache.

IIS often has 500 errors in actual use, and sometimes there is a strange phenomenon of suspended animation. Users need to restart the IIS service on an irregular basis to ensure that the site is normal.

Apache is more complex to configure than IIS, but it can work long-term once it's set up. Large Web sites use Apache as their own WWW service provider. All Apache configuration is saved in the configuration file and is executed exactly as it was logged in the configuration file. In general, there will be no unexplained suspended animation situation.

Tip: Using IIS under the WINDOWS2003 system is better than Apache performance.

Conclusion--apache stability, IIS sometimes suspended animation, the former accounted for excellent.

Third, the expansion of:

Extensibility refers to whether the WWW service provider can be applied to a variety of situations, multiple network situations, and multiple operating systems.

IIS can only be used under Microsoft's Windows operating system, leaving windows he will accomplish nothing. Cannot be ported to other types of operating systems.

Apache is an all-rounder, he is not only used in Windows, for Unix,linux and FreeBSD and many other operating systems, he can be competent to work. And the configuration steps of different operating systems are basically similar, portability is very high.

Conclusion--iis can only run under Windows, Apache has a wide range of applications. Apache wins.
Iv. Security:

Often see such a site is hacked or a site by an illegal user upload virus message, for others to provide services for 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 had a big problem with security, and hackers could easily swoop in if the default settings were used. In IIS6, however, Microsoft has made significant improvements in its security. As long as the operating system Patches update timely, you can improve the safety of the site as much as possible. In particular, IIS6 and the. NET platform rely on each other to make security almost perfect.

Apache has been doing a good job in security, because many users are using Apache under Linux, so the characteristics of the operating system makes the Apache under Linux has a congenital umbrella, security naturally have no say.

Conclusion--IIS6 Previous versions have security implications, and IIS6 is as safe and reliable as Apache. IIS6 a tie with Apache.

V. Openness:

The so-called openness refers to whether to open the source code of the program, it is well known that IIS is a part of the Windows system, so his source code is not open. And Apache is different, the earliest he is for Unix-like system services, so completely open source code. Anyone can analyze his code, discover the vulnerabilities, and release patches to compensate for the vulnerability.

Because of this openness of Apache, it also makes its security greatly improved.

Conclusion--iis is not open code, Apache open source code. The latter won.

Six, the ease of:

The ease with which a tool is used directly affects how much of its users, especially Web publishing tools. After all, many companies want to have their own website, 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 easy to open, and it's easy for IIS to work and publish Web sites. However, administrators are prone to misconfiguration and mis-operation issues. But in general IIS is very easy to learn, but it is very difficult to learn him well.

Apache is more difficult to use than IIS and requires people with a certain computer and network Foundation to use. His configuration is not graphical and needs to be done by editing the configuration file. However, from the Apache settings, as long as we strictly follow the Help file for parameter settings, there is no difficulty.

Conclusion--iis is easy to install but difficult to master, Apache installation is relatively difficult, to be proficient is not an easy thing. IIS has a slight advantage.

Seven, Programming:

In order to make the web more colorful, more beautiful, more interactive, the master for us to develop a variety of components and controls, then these controls in IIS or Apache is working properly?

The MoD rewrite under APACHE is very powerful, while the rewrite of ISAPI in IIS needs to be developed specifically, which is not achievable by beginners. Apache can use Subversion WebDev as well as the. htaccess feature, and you can also use Forcetype. In addition, IIS support for fastcgi is not very good, so some CGI, PHP programs run slowly, far inferior to Apache.

Conclusion-different components are used in different environments, because the choice of IIS or Apache is determined by the work environment.

Viii. Language Support:

There are a variety of languages, such as asp,php,jsp, that currently create websites and forums. So does IIS and Apache support them?

IIS is stable for ASP, especially. NET, but it is more cumbersome for PHP and JSPs. PHP needs to be repeatedly configured to be supported on windows2003. Apache is well-supported in several of the languages mentioned above and runs asp,php,jsp without any problems.

Conclusion--apache supports a lot of languages, IIS is a bit cumbersome to support PHP and JSP, and requires some configuration. Apache wins.

Ix. Treatment:

Mention of the treatment may be a lot of readers will be puzzled, how IIS and Apache still have the treatment problem? What we are going to discuss here is the treatment of the network administrator. An IIS network administrator with an Apache network administrator, their salary is not the same.

The biggest advantage of Apache is that the configuration parameters are many, if you want to proficient in Apache requires a high level. So the same level of network administrator will be Apache than will be the treatment of IIS better.

Conclusion-more money is the only standard for winning, Apache is superior.

Summarize:

In fact, we are here today to argue that IIS good or Apache good is not very significant, the comparison of this article is only for those wandering in the network administrator intersection, do not know which tool to learn to build a website reader a little reference. You can plan for your future only if you have a general understanding of IIS and Apache.

In general, the advantage of Apache lies in a variety of open-source WWW service provider of the most comprehensive features, support the broadest, relatively stable, and rich in scalability. However, because of the scalability, performance will certainly not be too high, can only maintain a moderate level. IIS6 is still very powerful in handling connectivity and event performance, surpassing Apache. In addition the security aspect IIS6 also has the qualitative leap, has made up the past IIS flaw in the sky flaw. If your company is not responsible for the network environment, it does not involve too much development, the proposal still uses IIS6. Of course, if it is built on the WWW development and debugging or using Apache more comfortable.

Summarize:

Tomcat server is a free open source Web application server, belongs to the lightweight application server, in small and medium-sized systems and concurrent access users are not widely used, is the first choice to develop and debug JSP programs. For a beginner, it can be thought that when the Apache server is configured on a single machine, it can respond to requests for access to the HTML (one application under the standard Universal Markup Language) page. The tomcat part is actually an extension of the Apache server, but it runs independently, so when you run Tomcat, it actually runs separately as a separate process from Apache.

The trick is that when configured correctly, Apache serves HTML pages, while Tomcat actually runs JSP pages and Servlets. In addition, like a Web server such as IIS, Tomcat has the ability to handle HTML pages, and it is also a servlet and JSP container, and the standalone servlet container is the default mode for Tomcat. However, Tomcat is less capable of handling static HTML than the Apache server. Currently, the latest version of Tomcat is 9.0.

Citation Links:

Comparison between the Iis,apache,tomcat of Web servers

Web server, Application server, HTTP server differences

Baidu Encyclopedia: Web Server

Comparison of Iis,apache,tomcat between Web servers