Jetty can handle a large number of connections at the same time and maintain connections for a long time, making it suitable for web chat applications and so on. Jetty has a simple architecture, so as a server, Jetty can load components on demand, reduce unnecessary components, and reduce server memory overhead, thus improving server performance. Jetty uses NIO termination by default, which is more advantageous in processing I/O requests. When processing static resources, Tomcat has higher performance and is suitable for processing a small number of very busy links. In other words, if the link life cycle is short, Tomcat's overall performance is higher. Tomcat uses BIO to handle I/O requests by default, and its performance is poor when processing static resources.