GlassFish vs Apache Tomcat: What are the differences?
Developers describe GlassFish as "The Open Source Java EE Reference Implementation". An Application Server means, It can manage Java EE applications You should use GlassFish for Java EE enterprise applications. The need for a seperate Web server is mostly needed in a production environment. On the other hand, Apache Tomcat is detailed as "An open source software implementation of the Java Servlet and JavaServer Pages technologies". Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.
GlassFish and Apache Tomcat can be primarily classified as "Web Servers" tools.
Apache Tomcat is an open source tool with 3.51K GitHub stars and 2.4K GitHub forks. Here's a link to Apache Tomcat's open source repository on GitHub.
What is GlassFish?
What is Apache Tomcat?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose GlassFish?
What are the cons of using GlassFish?
What are the cons of using Apache Tomcat?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Apache Tomcat is part of the open source Ant Media Server platform that currently provides both LIVE and VOD video trans-coding and delivery features for the Promethean Platform.
J2EE application server to handle JDBC connection pooling, shared SDK, JDNI resources, etc. and host our JVM-based web applications (primarily Rails via JRuby).
I use Tomcat to run Java enterprise web apps. Used to test enterprise applications mostly written using the Spring framework
Use this as the application server running on our production and development environment. Hosted on AWS.
Tomcat provides a fantastic application container that runs the majority of services of the site.