Discussions

News: The great Java app server debate with Liberty and Jetty

  1. **IBM Liberty Profile**

    As the Liberty Profile is new and rapidly moving, it looks like the biggest focus is on feature and technology support rather than some of the fluffier aspects such as UI and migration, but it needs to focus on these aspects because in reality, devs will be comparing this server to Tomcat and Glassfish which have already been around for many years and the Liberty Profile is playing a catch up game to these servers.

    Overall, the Liberty Profile is one of the fastest changing and most interesting app servers to watch on the market today. Don’t look at it as just another WebSphere app server, take a look at it with a fresh and open mind and you might be impressed with it. The new Beta is just as exciting with some great new features.

    On the downside, it comes at a cost. Yes, development is free, but the world doesn’t stop at development and the cost curve to use it outside of development is very steep, particularly in comparison to other lightweight servers out there today, many of which are free.

    Read the full post here: http://zeroturnaround.com/labs/the-great-java-application-server-debate-ibm-liberty-profile/

    **Jetty**

    Jetty is an extremely lightweight server with options to easily configure and extend it. It was initially developed in 1995 and over 18 years of development it has preserved its lightweight size and simplicity.

    And let’s get this out the way...is Jetty a servlet container, or an application server?

    Jetty can host web applications and serve requests, so we consider it an application server. If you feel so strongly that you must object, feel free to knock your coffee over and kick the cat to get to your keyboard and type in your flame war opinion in our comments section.

    Jetty is not equipped with advanced management console and tools and this makes it hard to scale and configure in bigger environments. Operations team may get very frustrated and create inconsistencies when dealing with changes to some XML or property files on multiple servers. Jetty does need still some better tooling, both on the management and development sides.

    Read the full post here: http://zeroturnaround.com/labs/the-great-java-application-server-debate-jetty/

    Edited by: Cameron McKenzie on Apr 23, 2013 11:03 AM

    Threaded Messages (5)

  2. Announcement was today[ Go to top ]

    IBM made the announcement of WebSphere 8.5.5 today. There's a new offering called WAS Liberty Core which is Liberty without "full WAS". It'll be interesting to see what the pricing is on this... it stands to reason that IBM will want to put it at a low-ish price point.
  3. Jetty can serve requests[ Go to top ]

    Jetty can host web applications and serve requests, so we consider it an application server.
    So can apache, is it an app server?
  4. Jetty can serve requests[ Go to top ]

    If Apache HTTPD is running PHP apps or Ruby apps... They are just not Java EE Application Servers. Well, not right out of the box.
  5. Jetty can serve requests[ Go to top ]

    Well, that's just my point. Java EE is a whole spec, you have full-blown servers which are implementing it, and some servlet containers which don't. There is a point in making a difference.
  6. Jetty can serve requests[ Go to top ]

    Right. We do need to differentiate. But just because in our Java dev minds if it doesn't implement the whole Java EE spec it means it isn't an app server doesn't mean it actually is not. "Jetty can serve requests" - that is what most servers do. The difference is what they do under the covers - for instance - http://tomee.apache.org/