Why would it be preferred over Tomcat?
Is your experience with big or little companies? Internal or external (customer/public facing) systems?
Jetty is in a lot of production environments. It is very easy to install, configure and deploy on. No fluffy management stuff that gets in the way.
Jetty provides a web server and servlet container, additionally providing support for HTTP/2, WebSocket, OSGi, JMX, JNDI, JAAS and many other integrations. These components are open source and are freely available for commercial use and distribution.
Tomcat is an Apache project, while Jetty is managed by the Eclipse Foundation. In terms of licensing, Tomcat enjoys the Apache 2.0 open source license, while Jetty is dual licensed through both the Apache 2.0 License and the Eclipse Public License 1.0.
The easiest way to deploy a web application to Jetty server is probably by copying the WAR file into the $JETTY_HOME/webapps directory. Jetty will scan its $JETTY_HOME/webapps directory at startup for web applications to deploy. Our new app will be deployed at /jetty-app context.
You could look at this page listing products that use Jetty.
One example you might (unknowingly) be familiar with is that the Eclipse IDE's help system uses Jetty.
Google App Engine for Java (GAE/J) uses Jetty as servlet container.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With