Jetty vs. Tomcat_jetty

Jetty more memory-saving, simple, compact configuration simpler features can be plugged out, do not need to be removed to save memory, such as the session processor based on the handler architecture, expansion of simple, convenient for its two development suitable for embedding into small devices, such as mobile phones and set-top boxes Can be easily embedded in the application, such as Hadoop, SOLR is the jetty as a Web server Jetty-maven plug-in allows applications to not be packaged into a war can be run by default NIO is more suitable for processing long connections, such as Web chat applications if you deploy multiple applications at the same time, The error rate is higher and the resource consumption is more than the case with slow and high concurrency.
Tomcat memory footprint a little bit more complex configuration is more complicated based on the design of the container, the expansion is more troublesome Tomcat7 default use of BIO,TOMCAT8 also defaults to use NIO (reference: http://blog.csdn.net/clementad/article/ details/47045673) is more suitable for dealing with short connections, such as a large number of API interface calls to better support the simultaneous deployment of multiple applications in the case of high concurrency, the error rate is relatively small, resource consumption is less
More about Tomcat: http://blog.csdn.net/clementad/article/details/46842309
Summary: Jetty suitable for user-less, simple, or small devices embedded application tomcat suitable for high concurrency, request frequent application
In addition, the difference between JBoss and Tomcat: http://blog.csdn.net/clementad/article/details/46821077


(Original article, reprint please indicate the CSDN blog that has been transferred from Clement-xu.) ）