Community version called Application Server (AS) - this will have only community support.This includes Tomcat as web container internally. This is a full-stack support for JavaEE and it is a certified Java EE container. No commercial support available (only community support) Tomcat EE - This is a certified Java EE container, this supports all Java EE technologies.Tomcat - Web profile - lightweight which is only servlet container and does not support Java EE features like EJB, JMS etc.
![tomcat vs glassfish performance tomcat vs glassfish performance](https://image.slidesharecdn.com/interconnect-wasvsjbossvsweblogicvstomcat-150227191612-conversion-gate02-150429140520-conversion-gate01/95/websphere-app-server-vs-jboss-vs-weblogic-vs-tomcat-4-638.jpg)
Tomcat - is run by Apache community - Open source and has two flavors: Java EE applications (usually both servlet/JSP and EJBs). Tomcat) means: It can handleĪn Application Server (e.g. You should use GlassFish for Java EE enterprise applications.Ī web Server means: Handling HTTP requests (usually fromĪ Servlet Container (e.g. JBoss is NOT under the control of Sun/Oracle, with all the advantages THAT can offer. GlassFish comes straight from Sun/Oracle, with all the advantages that can offer. GlassFish's admin console is extremely slick, whereas most administration in JBoss is done with a command-line and text editor. Also, for those who prefer a GUI-based admin system. However, JBoss lags significantly behind GlassFish in implementing the current Java EE specs. JBoss has a larger and deeper user community, and a more mature codebase.
#Tomcat vs glassfish performance free#
JBoss and GlassFish are two of the most popular open source offerings (the third one is Apache Geronimo, upon which the free version of IBM WebSphere is built).
#Tomcat vs glassfish performance full#
However, for applications that do require a full Java EE stack (or at least more pieces that could easily be bolted-on to Tomcat). Administration of a Tomcat server is arguably easier, as there are fewer moving parts. Tomcat is very popular for simple web applications, or applications using frameworks such as Spring that do not require a full Java EE server. On the other hand, Tomcat has a lighter memory footprint (~60-70 MB), while those Java EE servers weigh in at hundreds of megs.
![tomcat vs glassfish performance tomcat vs glassfish performance](http://www.jmjcloud.com/uploads/7/8/4/7/78474242/tomcat.jpeg)
JBoss and GlassFish are full-blown Java EE application servers, including an EJB container and all the other features of that stack. Tomcat is merely an HTTP server and Java servlet container.