Apache TomEE vs. Apache Tomcat vs. Eclipse Jetty vs. Python Comparison Chart

Apache TomEE, pronounced “Tommy”, is an all-Apache Jakarta EE 9.1 certified application server that extends Apache Tomcat that is assembled from a vanilla Apache Tomcat zip file. We start with Apache Tomcat, add our jars, and zip up the rest. The result is Tomcat plus EE features, TomEE. Stable and ready for production, Apache TomEE 8.0 implements Java EE 8/Jakarta EE 8 and supports the javax namespace. Runs on Java 8 or higher. Mostly Jakarta EE 9.1 web profile compliant and supports the new jakarta namespace. Runs on Java 11 or higher. Apache TomEE comes in four different flavors, web profile, MicroProfile, Plus and Plume. Apache TomEE web profile delivers servlets, JSP, JSF, JTA, JPA, CDI, bean validation and EJB Lite. Apache TomEE MicroProfile adds support for MicroProfile. Apache TomEE Plus and Plume add support for JMS, JAX-WS, and more. Mostly Jakarta EE 9.1 Web Profile compliant and supports the new jakarta namespace.

Jetty provides a web server and servlet container, additionally providing support for HTTP/2, WebSocket, OSGi, JMX, JNDI, JAAS and many other integrations. These components are open source and are freely available for commercial use and distribution. Jetty is used in a wide variety of projects and products, both in development and production. Jetty has long been loved by developers due to its long history of being easily embedded in devices, tools, frameworks, application servers, and modern cloud services. Full-featured and standards-based. Open source and commercially usable, flexible and extensible, small footprint, embeddable, asynchronous, enterprise scalable, and dual-licensed under Apache and Eclipse. Large clusters, such as Facebook Presto. Cloud computing, such as Google AppEngine. With the direction of Java and the JakartaEE project (formerly JavaEE) in 2020, the current recommended version of Jetty for use depends upon the servlet API version, desired licensing, etc.