13 Responses to “Poll: What is your Application Server of choice?”

1. Ryan
   September 30th, 2007 @ 00:56

   Why isn’t Glassfish V2/Sun Application Server listed?

2. Kenneth
   September 30th, 2007 @ 08:51

   Agree with you Ryan. My favorite is Glassfish V2

3. Clara Ko
   September 30th, 2007 @ 10:50

   Added Glassfish Application Server and moved both of your votes from Other

4. JavaDev
   September 30th, 2007 @ 20:17

   Currently, my favorite is Resin: very fast, light, simple.

5. Francois
   October 1st, 2007 @ 13:31

   +1 for Resin

6. Graeme Wicksted
   October 1st, 2007 @ 15:52

   +1 for Sun App Server

7. eduardo pelegri-llopart
   October 1st, 2007 @ 17:07

   re: Sun App Server - Since SJS AS 9.x are just branded (and supported) distributions of GlassFish (v1/v2); I think this would fall under the GlassFish bucket… - eduard/o

8. Clara Ko
   October 2nd, 2007 @ 14:27

   Added Resin and moved 2 votes from Other according to comments

9. Clara Ko
   October 2nd, 2007 @ 14:27

   Moved Graeme’s vote from Other to Sun App Server.

10. Kees Broenink
    October 12th, 2007 @ 08:42

    I am missing the most popular Java container Tomcat. And Jetty should be on the list too. Are we not calling them application server because they do not support EJB? I can write an enterprise web application with JSF, Spring and Hibernate and deploy it as a WAR. So let’s call those containers application server too.

11. Clara Ko
    October 15th, 2007 @ 13:01

    Kees,

    There are differences between a web server and an application server. Application servers usually include more features than web servers.

    The following are common features of application servers (from an entry in Sun’s Java forum):

    1. Scalability *
    2. Performance *
    3. Messaging
    4. Resource Pooling
    5. JNDI
    6. Transaction services
    7. In-Built Security
    8. App Diagnostics & Monitoring
    9. In-Built IDEs eg: workshop for weblogic, WSAD for WebSphere

    I think 1, 2, and 9 are kind of off topic, but the rest are used in most enterprise applications.

12. Kees Broenink
    October 22nd, 2007 @ 18:24

    Clara,

    A lot of enterprise applications do not use EJB and messaging so do not feel the need for JNDI. The pooling is normally done by hooking up an extra library with Hibernate. Same for transaction services. When using Spring you will have also great support for security. So I fail to see the reason to use a ‘real’ application server. Jetty is more scalable and has a better performance than WebSphere and WebLogic…
    Of course I am trying to play a bit with words here too. I am really not a fan of the way application servers are put in the market. People pay far too much money for functionality they can have for free in a better way using Spring.
    Portal servers are a different ball game. There you get extra functionality for your money and indeed integration with IDE is an important one.

    Kees

13. John Eastwood
    December 16th, 2007 @ 14:12

    This is a POJO Application Server… its a new concept and it kicks butt.
    At last someone was brave enough to say EJB sucks, and come up with something thats, easy, faster, and more powerful.

Leave a Reply