What is GlassFish Hosting?
Unlike, Tomcat, GlassFish server is a full application server. Because most any application that runs on Tomcat can be run without any changes on GlassFish, many people think that Tomcat is a full application server. It is not because, typically, if you want solid HTTP performance from it, you need the Apache web server sitting in front of it.
GlassFish has the Grizzly framework as its HTTP frontend. Grizzly takes advantage of the Java New I/O API (NIO). With Grizzly, GlassFish can take advantage of its HTTP Protocol (for creating custom HTTP applications) and its HTTP Server framework (allows for high level abstractions to the HTTP Protocol-like Servlets).
GlassFish is the Reference implementation of Java EE. Because of that, it supports JavaServer Pages, servlets, Enterprise JavaBeans, Java Persistence API (JPA), JavaServer Faces, Java Message Service (JMS) and a lot more. With GlassFish web service, developers can develop enterprise applications that not only integrate with legacy technologies but are scalable and portable.
GlassFish started back in June of 2005. By May of the next year, the first version, which supported the Java EE 5 specifications, was released. In 2010, the project changed hands when Oracle acquired Sun. Of the many updates and features that were added along the way, the ones that are most talked about as the benefits of GlassFish now are its clustering ability, its performance, load-balancing capabilities and the wide range of supported components.
Full clustering is built right into GlassFish. There is no need for other codebases or to find another solution for your clustering needs. This can provide you with some major advantages when deploying your Java applications.
Project Shoal is the sub-project in GlassFish that allows it to provide these features. One of the huge benefits of the clustering technology that Project Shoal provides is that GlassFish doesn't make any assumptions about what kind of load-balancing is being used, whether software or hardware. It has Web Server plugins that work with both kinds of load balancers.
We kept native GlassFish clustering architecture, allowing you to take advantage of its clustering technology, as well as adding one-click scaling and replication for your running instances.
The clustering architecture that Glass Fish uses is based on the concept of administrative domain, which consists of clusters and instances and controlled by a Domain Administration Server (DAS).
GlassFish Server Performance
One of the biggest benefits that you get from GlassFish support is its high level of performance. This is mainly due to Sun's commitment to, and years of work on, the performance of GlassFish-Servlet containers, Web Services, OpenMQ, Grizzly, Enterprise JavaBeans containers and more. This was first evidenced in 2007 when GlassFish set a world record in the SPECjAppServer benchmark. Sun has made it to where you don't have to choose between open-source and performance. Java GlassFish is heavy on performance.
How do I use GlassFish Hosting with Jelastic?
When you are creating your Java environment in Jelastic, just select GlassFish free application server hosting from the drop down menu. Itâs that easy.
How do I get started using Jelastic?
It's easy. Go here and follow the easy instructions to get going!