By Herring on Apr 28, 2009
At the MySQL User Conference last week I had a number of attendees come up to me to ask which application server they should be using with MySQL. They were looking for something that was fast, lightweight and compatible. To me the choice was obvious -- GlassFish!
So why GlassFish?
Project GlassFish, was launched when Sun open-sourced its application server and the Java EE Reference Implementation, was Sun's first step toward open-sourcing the entire Java platform. Less than a year after the initial launch, the GlassFish community delivered the first release of the GlassFish Application Server, a production-quality, Java EE-compliant application server, followed by a second release in 2007. Today, GlassFish is the leading open-source and open community platform for building and deploying next-generation applications and services. The GlassFish application server has been downloaded more than 18 million times since 2006.
Another choice might be Red Hat's JBoss application server that was released in 2006. Although JBoss has had some success in the past, I would caution that there are some issues around backward compatibility and features that are not supported in the commercial release of the product. In addition it seems to be pretty far behind as far as latest features around JavaEE are concerned.
In contrast, the GlassFish application server is backward-compatible; features released today will be supported in future freely available versions as well as future Sun-supported commercial versions of GlassFish Enterprise Server. Additionally, the freely available GlassFish application server is ready for production right out of the box. For these reasons, I recommend GlassFish application server over JBoss!
Tomcat application server is extremely popular with Java developers who only want to only use servlets, but it doesn't support the full Java EE stack. So why use only a bit of Java when you can use the full reference implementation?