Databases
StackOverflow2013
Postsdbo
POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
    primarykey
    data
    text
    <p>I have several webapps deployed to production. I have used Tomcat as my servlet engine for ~10 years now. I'm considering moving to embedding Jetty model from the deploy-a-war-into-Tomcat model.</p> <p>These webapps are deployed over several servers and some of the are horizontally scaled (using nginx IP hash based partitioning).</p> <p>I see some advantages:</p> <ul> <li><p>I can configure my servlet engine for a particular webapp (instead of having a generic configuration for Tomcat which is running several different webapps)</p></li> <li><p>It's easier to horizontally scale my webapp by running multiple Jetty instances (configured to listen on different ports) on the same host. I could also do this with Tomcat (and I have run multiple tomcat instance on the same host in the past), but I've moved to using Debian packages (.deb archives) for deployment and it's not as easy to run multiple Tomcats using this method.</p></li> <li><p>My deployment package (.deb) is more "complete" at build time i.e. I don't have to be sure the Tomcat instance is configured correctly.</p></li> </ul> <p>And disadvantages:</p> <ul> <li><p>More instances of a servlet engine running on a server means more resources being used</p></li> <li><p>I've never used Jetty. I don't think I have any Tomcat-specific stuff going on in my webapps, but I'm not sure.</p></li> </ul> <p>My main concern is the amount of resources that Jetty will use. If I had one Tomcat instance running 4 webapps, what will the difference in resources (memory/processor) be with four Jetty instances running?</p> <p>This question is probably too open-ended, but I'm curious to know if I'm overlooking something or if anybody has any experience moving from Tomcat to (embedded) Jetty.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USthree-cups
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
      1. USJeremy
      1. VTFavorite
    3. VO
      singulars
      1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOne other note: running multiple servlet processes means that each process will have it's own port. Said another way, separate processes cannot share a single port.
      singulars
      1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
      1. USthree-cups
    2. COI think my biggest problem with Jetty is all the options it gives! Tomcat makes you go one way. Jetty seems to let you do whatever you want.
      singulars
      1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
      1. USthree-cups
    3. COI'm thinking of writing a generic jetty startup script that takes a port, and a list of webapp/context pairs. This seems like it would give me the most flexibility. Maybe there is already one of these scrips out there? I'm going to look at .../bin/jetty.sh in the jetty 7 distributions.
      singulars
      1. POJava Servlet Deployment - To Embed or Not - Tomcat/Jetty
      1. USthree-cups
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload