As of late on the IAM effort, we have been involved in an evaluation of application servers. Actually this is our second round of doing so. Last year, we did an evaluation of Mule, ServiceMix and Geronimo. At the time Geronimo, being fully Java 5 EE compliant, turned out to be a good choice for development. We liked it because it had a great plug-in for Eclipse and it met all of our needs at the time. As part of our project's functionality we needed to use Java Messaging Services (JMS). The problem we ran into with Geronimo was it did not support the STOMP protocol. So we re-grouped and switched to IBM's WebSphere Community Edition. The message problem was solved, we thought. Then we tired to use SSL for messaging and found the support in WebSphere CE to be lacking.
So, we commenced round #2, which included: Tomcat, WebSphere, JBoss and WebLogic. Since all of our Web Services were SOAP-based we needed a really good servlet container, which Tomcat is. However we needed other features like the messaging, which Tomcat does not provide, but the other products did. We ended up doing a lot of timing tests and evaluations and our winner is? WebLogic. It is a very fast Application Server, and it met all of our requirements. Since our development is going to be using Oracle, the tight integration between the database and the application server also made it an attractive choice. And the runner up was Tomcat BTW. Probably the best servlet container out there. Why did we not select it? Mainly because of having to add other tools either to it or standalone to meet the requirements that we have come up with. Timing results are below.
So, we commenced round #2, which included: Tomcat, WebSphere, JBoss and WebLogic. Since all of our Web Services were SOAP-based we needed a really good servlet container, which Tomcat is. However we needed other features like the messaging, which Tomcat does not provide, but the other products did. We ended up doing a lot of timing tests and evaluations and our winner is? WebLogic. It is a very fast Application Server, and it met all of our requirements. Since our development is going to be using Oracle, the tight integration between the database and the application server also made it an attractive choice. And the runner up was Tomcat BTW. Probably the best servlet container out there. Why did we not select it? Mainly because of having to add other tools either to it or standalone to meet the requirements that we have come up with. Timing results are below.
Recent Comments