The difference between IIS-Apache-Tomcat The difference between
IIS and Tomcat
IIS is Microsoft's Web server. Mainly supports ASP language environment.
Tomcat is the standard implementation of Java Servlet 2.2 and JavaServer Pages 1.1 technology. It is based on the SJP language environment container developed under the Apache license. Strictly speaking, it is not a WEB server, but an Apache service adapter.
The main task of tomcat is not WEB service, but to support the JSP language environment.
IIS is also a WEB server, which supports the ASP language environment
. The difference between Apache and Tomcat
APACHE is a web server environment program. It can be used 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 jsp web pages, and this jsp interpreter is TOMCAT, why do you need JDK? Because jsp needs to connect to the database, jdk is required to provide the driver to connect to the database, so APACHE+TOMCAT+JDK is required to run the web server platform of jsp. The advantage of integration is: if the client requests a static page, only Apache is required The server responds to the request If the client requests a dynamic page, it is the Tomcat server that responds to the request. Because jsp is the server-side interpreted code, this integration can reduce the service overhead of Tomcat.
Apache is a web server, tomcat is an application (java) server, it is only A servlet (jsp is also translated into servlet) container, which can be considered as an extension of apache.
Apache: ordinary server, it only supports html, that is, ordinary web pages. It is an html container and functions like IIS.
tomcat: Explains java programs (jsp, serverlet), it is a jsp/servlet container, and
apache used to publish JSP and JAVA is a truck, which can hold some things such as html. But it can't hold water. To hold water, you must have a container (bucket). The tomcat is a bucket (for water like JAVA), and this bucket can also not be placed on the truck.
The difference between IIS and Apache
It is the most common thing for small and medium-sized enterprises to build their own websites and display their own pages to the outside world. Currently the most popular tools for building WWW services are Apache and IIS. So what is the difference between them? Which tool is the most suitable for us? Let's discuss this issue today.
1. The debate between free and charging:
Although many users use IIS to build websites, it is a component integrated in the Windows operating system. However, if you want to use IIS legally, you need to buy a genuine Windows operating system.
On the other hand, Apache is completely free. It's free to download and use without paying anything.
Conclusion - Apache is free, IIS is charged, the former is dominant.
2. Stability:
The next thing to compare is stability. The WWW service needs to run normally at any time, and a website needs to be open to the public 24 hours a day, seven days a week. So stability is the focus of the comparison between IIS and APACHE.
IIS often has 500 errors in actual use, and sometimes there is an inexplicable suspended animation. Users need to restart the IIS service from time to time to ensure the normal operation of the website.
Apache is more complicated to configure than IIS, but once set up it can work for a long time. Large websites use APACHE as their WWW service provider. All configurations of APACHE are saved in the configuration file, and the use is performed in accordance with the information recorded in the configuration file. Inexplicable suspended animation usually does not occur.
Tips: Using IIS under windows2003 system is better than using APACHE.
Conclusion - APACHE stable, IIS sometimes suspended animation, the former dominant.
3. Scalability:
Scalability refers to whether the WWW service provision tool can be applied to various occasions, various network conditions, and various operating systems.
IIS can only be used under Microsoft's windows operating system, and he will be nothing without windows. Not portable to other types of operating systems.
APACHE is an all-rounder, he is not only used in windows, he can be competent for various operating systems such as unix, linux and freebsd. Moreover, the configuration steps of different operating systems are basically similar, and the portability is very high.
Conclusion - IIS can only run under windows, apache has a wide range of applications. apache wins.
4. Security:
We often see news that a certain website has been attacked by hackers or that a certain website has been uploaded by an illegal user. For a site that provides services to others, security is the most important. If a website does not even guarantee its own security, who wants to browse and use it.
In the early days of IIS, there was a big problem in terms of security. If the default settings were used, hackers could easily take advantage of it. However, in IIS6, Microsoft has made significant improvements in security. As long as the operating system patches are updated in a timely manner, the safety factor of the website can be improved as much as possible. In particular, IIS6 and the .net platform rely on each other to make security almost perfect.
APACHE has always done a good job in security, because many users are using apache under linux, so the characteristics of the operating system make apache under linux have an innate umbrella, and the security naturally has nothing to say.
Conclusion - The previous version of IIS6 has security risks, IIS6 is as safe and reliable as APACHE. IIS6 is tied with APACHE.
5. Openness:
The so-called openness refers to whether the source code of the program is opened. As we all know, IIS is a part of the WINDOWS system, so his source code is not open. Apache is different. At first, it served for Unix-like systems, so it is completely open source code to the outside world. Anyone can analyze his code, find a bug in it, and release a patch to fix it.
It is precisely because of the openness of APACHE that its security is greatly improved.
Conclusion - IIS is not open source, APACHE is open source. The latter wins.
6. Difficulty:
The ease of use of a tool directly affects the number of its users, especially web publishing tools. After all, many companies want to have their own website, but they don't want to hire a high-paid webmaster to maintain it. Therefore, you must find tools that are relatively easy to use to build your own site.
IIS is relatively simple to open, and it is easy to make IIS work and publish websites to the outside world. However, administrators are prone to misconfigurations and misoperations. But in general, IIS is still very easy to learn, but it is probably very difficult to learn him well.
The use of APACHE is more difficult than that of IIS, and it requires people with a certain computer and network foundation to use it. His configuration is not graphical, we need to edit the configuration file to achieve. But from the APACHE setting alone, as long as we set the parameters strictly according to the help file, there is no difficulty.
Conclusion - IIS is easy to install but difficult to master, APACHE is relatively difficult to install, and it is not easy to master. IIS has a slight advantage.
7. Programmability:
In order to make the web page more colorful, more beautiful and more interactive, experts have developed a variety of components and controls for us, so do these controls work normally under IIS or APACHE?
The Mod Rewrite function under APACHE is very powerful, while the Rewrite of ISAPI in IIS needs to be specially developed, which is generally impossible for beginners. APACHE can use Subversion WebDev and .htaccess functions, and can also use ForceType. In addition, IIS's support for FastCGI is not very good, so some CGI and PHP programs run very slowly, far less than apache.
Conclusion - Different components are used in different environments, because the choice of IIS or APACHE is determined by the working environment, and the two are indistinguishable.
8. Supporting languages:
As there are various languages for building websites and forums, such as ASP, PHP, JSP and other languages. So do IIS and APACHE support them?
IIS is very stable for ASP, especially .net, but it is more troublesome for PHP and JSP. PHP needs to be reconfigured to be supported on Windows 2003. APACHE can support several languages mentioned above very well, and run ASP, PHP, JSP without any problem.
Conclusion - APACHE supports many languages, and IIS is a little troublesome when it supports PHP and JSP, and needs to go through a certain configuration. APACHE wins.
Nine, treatment: When it comes
to treatment, many readers may be more puzzled, why is there still treatment problems in IIS and APACHE? In fact, what we want to discuss here is the treatment of network administrators. A network administrator who can IIS and a network administrator who can APACHE, their salary is not the same.
The biggest advantage of APACHE is that there are many configuration parameters. If you want to be proficient in APACHE, you need a high level. Therefore, the same level of network administrators will APACHE will be better than the treatment of IIS.
Conclusion - more money is the only criterion for winning, APACHE prevails.
Summarize:
In fact, it is meaningless to argue whether IIS or APACHE is better today. The comparison in this article is only a reference for readers who are wandering at the intersection of network administrators and do not know which tool to learn to build a website. Only after you have a general understanding of IIS and APACHE can you plan for your future.
In general, the advantages of Apache are that it has the most complete features, widest support, relatively stable, and rich extensibility among various open source WWW service providers. However, just because the scalability is considered, the performance will definitely not be too high, and it can only maintain a medium level. And IIS6 is still very powerful in handling connection and event performance, surpassing APACHE. In addition, in terms of security, IIS6 has also made a qualitative leap, making up for the defects of IIS vulnerabilities in the past. If your company's network environment is not responsible and does not involve too much development, it is recommended to still use IIS6. Of course, if it is based on WWW development and debugging, it is more convenient to use APACHE.
Summarize:
Tomcat server is a free and open source Web application server. It is a lightweight application server. It is widely used in small and medium-sized systems and occasions where there are not many concurrent users. It is the first choice for developing and debugging JSP programs. For a beginner, it can be thought that when the Apache server is configured on a machine, it can be used to respond to the access request of HTML (an application under the standard general markup language) page. Actually the Tomcat part is an extension of the Apache server, but it runs independently, so when you run tomcat, it actually runs 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, Tomcat, like Web servers such as IIS, has the function of processing HTML pages. In addition, it is also a Servlet and JSP container. The independent Servlet container is the default mode of Tomcat. However, Tomcat is not as good at handling static HTML as the Apache server. Currently the latest version of Tomcat is 9.0
Reprinted source: https://www.cnblogs.com/rainbow70626/p/6048709.html