Tomcat VS Jetty

JavaTomcatServletsWebserverJetty

Java Problem Overview


I'm wondering about the downsides of each servers in respect to a production environment. Did anyone have big problems with one of the features? Performance, etc. I also quickly took a look at the new Glassfish, does it match up the simple servlet containers (it seems to have a good management interface at least)?

Java Solutions


Solution 1 - Java

I love Jetty for its low maintenance cost. It's just unpack and it's ready to roll. Tomcat is a bit high maintenance, requires more configuration and it's heavier. Besides, Jetty's continuations are very cool.

EDIT: In 2013, there are reports that Tomcat has gotten easier. See comments. I haven't verified that.

Solution 2 - Java

I think tomcat is more disscussed and supported by application, Jetty is portable and can be embedded in an application. and Jetty has good continuations.

Solution 3 - Java

I like how Jetty can be embedded in an application so that it doesn't need to run in a web container (Hudson and Nexus are two apps that can run in this mode). Can Tomcat do this?

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionLokiView Question on Stackoverflow
Solution 1 - JavaVinko VrsalovicView Answer on Stackoverflow
Solution 2 - JavaJimmy SubbView Answer on Stackoverflow
Solution 3 - JavaAndrew SwanView Answer on Stackoverflow