BACKGROUND IMAGE: iSTOCK/GETTY IMAGES
It was with a heavy heart that Oracle discontinued its production support of its Glassfish application server. But not having a 1-800 Oracle number to call when things go sideways with the latest edition shouldn't discourage organizations from putting this open source application server into production. After all, there are still compelling reasons to use Glassfish for more than testing, and those reasons extend far beyond the obvious fact that it can be deployed for free. "It's lighter, more modular, and easier to use and easier to develop for," especially when comparing the Glassfish server of today to application servers of the past, said Steve Millidge, founder and technical director at C2B2 Consulting.
The other compelling reason to use Glassfish is the fact that it remains the implementation standard for each new version of Java EE. So, if an organization wants to be first to market with some of the latest new features, Glassfish should be the target application server of choice. And of course, Glassfish is the de facto testing environment for NetBeans, so, if you're already developing and testing with NetBeans, it only makes sense to go into production with that exact same configuration.
Of course, few organizations could ever go live with a product that didn't come with full product support, but Millidge believes he's got that objection covered as well through Payara. "Payara is an initiative we are launching that provides 24/7 support for the Glassfish Open Source edition," he said. So, while it may not be an Oracle voice on the end of the support call line, organizations can indeed now get reliable software support for their production Glassfish instances. It might not actually be from Oracle, but as long as the support is reliable and effective, does it really matter who employs the individual on the other side of the support call?