Lighttpd vs. Oracle GlassFish Server

The benefits outweigh the costs, and the ability to spin up a full cluster deployment for our internal applications on demand has been a game changer. We are able to leverage our engineers' core talents as J2EE developers without them concerning themselves with the infrastructure machinery of managing a highly available fault-tolerant server.

Incentivized

• Oracle Glassfish servers provide us the ability to deploy in clusters and provide replication facilities.
• The server provides very easy administration console that can be used to tweak basic features for timeouts and database thread pooling.
• It can easily be configured for single sign on for enterprise clients.

Incentivized

• When we use the versions of GlassFish Server that were just released to the market, it causes bugs to appear. While there are workarounds to solve them in most cases, the amount of time to solve them is significant. Therefore, I would advise waiting for it to be a little more stable and for a few months to pass before proceeding to an update of a productive environment.

Incentivized

Tomcat is a more lightweight container in comparison to Oracle's Glassfish server and has wider adaptability in development for local testing. Glassfish however, as an enterprise product can offer better after sales service to clients.

Incentivized

• The platform has been stable for us so we do not experience falls or service interruptions. The investment is lower compared to other solutions in the market and we have solid support from Oracle.

Incentivized