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.
-Pivotal tc Server is best used as web application server on a virtual machine for middleware purposes -I feel it is less appropriate to be used with utilizing data that does not need to be secure
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.
User management and administration access account setup has room for improvement and can be more user friendly and clearly list how many admin accounts we can setup
password complexity for user accounts need to be updated
although all logs list all errors some of the tomcat errors are not time stamped
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.
We selected Pivotal tc Server opposed to Cent0s Linux because Pivotal tc Server is more reliable and causes less downtime , also better logging. I have used both
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.
