Summary: Apache/tomcat/jboss/jetty/nginx differences

Summary: Apache/tomcat/jboss/nginx differences.
1, Apache is a Web server, Tomcat is an application (Java) server. Tomcat is commonly used in small and medium-sized systems and in situations where concurrent access users are not many. Apache supports static pages, and Tomcat supports dynamic.
2. The Jetty:tomcat kernel acts as its servlet container engine and is reviewed and tuned. Large and medium-sized systems can be applied. The ability to provide database connection pooling services, and also support integration of other WEB technologies, such as PHP,. NET two camps.
3. JBoss is a container and server for managing EJBs, but the JBoss Core service does not include web containers that support servlet/jsp, typically used with Tomcat or jetty bindings.
4, Nginx is currently the highest performance HTTP server. It is characterized by the possession of less memory and strong concurrency. The Nginx code is completely written in C language from scratch.

So: Apache--nginx;tomcat--jetty;jboss. The three groups can be combined.

Specific Description:

First, Apache+tomcat
Apache supports static pages, and Tomcat supports dynamic, such as Servlets,
For general use of Apache+tomcat, Apache is just a forwarding, and the processing of JSPs is handled by Tomcat.
Apche can support Phpcgiperl, but to use Java, you need Tomcat to support the Apache backend, and the Java request will be forwarded to Tomcat for processing by Apache.
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, but can be run independently of Apache.

These two can be compared in the following points:
Both are developed by the Apache organization.
Both have the functionality of the HTTP service
Both are free.
Different points:
Apache is dedicated to providing HTTP services, and related configuration (such as virtual host, URL forwarding, etc.)
Tomcat is a JSP server developed under the Java EE JSP and the servlet standard: Tomcat is commonly used in small and medium-sized systems and in situations where concurrent access users are not many.

Second, Jetty

The jetty uses the industry's best open source Java Web engine to load the Java community the most, with the largest number of users, and the standard supports the most complete Tomcat kernel as its servlet container engine, which is reviewed and tuned. Simple Tomcat performance is limited and is lacking in many places, such as active connection support, static content, large files, and HTTPS. In addition to performance issues, the other big disadvantage of Tomcat is that it is a limited integration platform that only runs Java applications. When using Tomcat, the enterprise often needs to deploy Apache webserver to integrate with it. This configuration is cumbersome and does not guarantee the superiority of performance.
Jetty solves the many shortcomings of Tomcat by using a hybrid model of APR and Tomcat native technology. The hybrid technology model provides the best threading and event handling from the latest operating system technologies. As a result, the jetty achieves scalability, matching performance parameters even beyond the local Apache HTTP server or IIS. For example, jetty can provide database connection pooling services, not only support Java technology such as JSP, but also support the integration of other WEB technologies, such as PHP,. NET two camps.

Three, Nginx
Nginx has very high stability. Other HTTP servers, when encountering spikes in access, or when someone maliciously initiates a slow connection, are likely to cause the server to run out of physical memory frequently, lose response, and only restart the server. For example, once Apache has reached more than 200 processes, the Web response is significantly slower. Nginx adopts the phased resource allocation technology, which makes its CPU and memory occupancy rate very low. Nginx official said to maintain 10,000 inactive connections, it only accounted for 2.5M of memory, so a DOS-like attack on Nginx is basically useless. In terms of stability, Nginx is better than lighthttpd.

Iv. JBoss

JBoss a Java EE-based open source application server. JBoss is a container and server for managing EJBs, but the JBoss Core service does not include web containers that support servlet/jsp, and is typically used with Tomcat or jetty bindings.
JBoss and the Web server run the JBoss post-run backend management interface in the same Java virtual machine, and the servlet calls the EJB without the network, which greatly improves operational efficiency and improves security performance.

The above describes the summary: Apache/tomcat/jboss/jetty/nginx differences, including the aspects of the content, I hope that the PHP tutorial interested in a friend helpful.

