SailFin and GlassFish - How Are They Related?

SailFin and GlassFish

Prasad has written an Overview note explaining the relationship between SailFin and the core GlassFish AppServer. This expands on my earlier note and on Abhijit's note.

In a nutshell, GFv2.1 adds all the non-SIP specific features to the core GlassFish AppServer (building on the GFv2 UR1 release) and SailFin builds directly on that.


The blog entry was closed for comments, so I'll comment here instead.

What does the loadbalancing enhancements to support sailfin mean? Does it include making a special instance of glassfish / grizzly just tailored to loadbalance between backend GF instances? Perhaps this is not possible to do within reasonable resource constraints until GF3 makes it possible to load just a micro-container + grizzly connector.

Posted by Jesper Söderlund on October 08, 2007 at 05:33 PM PDT #

The current loadbalancer in GFv2 is based on the loadbalancer plugin from the SJSWS, which loadbalances only HTTP traffic.

The loadbalancer in Sailfin referred as the converged loadbalancer ( CLB) would need to support loadbalancing for both SIP and HTTP traffic and is a completely different loadbalancer than the loadbalancer plugin. The key difference is each Sailfin instance which also contains the CLB is a loadbalancer, is capable of redirecting the request to any Sailfin instance or handle the request itself. This functionality would not be available with plain GlassFishv2.1

To rephrase what you said, the CLB is a special Sailfin instance that is capable of loadbalancing between different Sailfin instances in the cluster.

Posted by Prasad Subramanian on October 09, 2007 at 12:47 AM PDT #

Jesper, I'm currently working on a load balancer build on top of Grizzly 1.6, that will works with v3 as well. This is not the one used in Sailfin, which extends Grizzly 1.0 instead of 1.6 and .....

Posted by Jeanfrancois Arcand on October 09, 2007 at 03:42 AM PDT #

That sounds good! I hope that it can include a transparent proxyoption so that the client's IP will be visible "through" the loadbalancer.


Posted by Jesper Söderlund on October 09, 2007 at 09:04 AM PDT #

Post a Comment:
Comments are closed for this entry.