Java Servlet Deployment - To Embed or Not - Tomcat/Jetty -


i have several webapps deployed production. have used tomcat servlet engine ~10 years now. i'm considering moving embedding jetty model deploy-a-war-into-tomcat model.

these webapps deployed on several servers , of horizontally scaled (using nginx ip hash based partitioning).

i see advantages:

  • i can configure servlet engine particular webapp (instead of having generic configuration tomcat running several different webapps)

  • it's easier horizontally scale webapp running multiple jetty instances (configured listen on different ports) on same host. tomcat (and have run multiple tomcat instance on same host in past), i've moved using debian packages (.deb archives) deployment , it's not easy run multiple tomcats using method.

  • my deployment package (.deb) more "complete" @ build time i.e. don't have sure tomcat instance configured correctly.

and disadvantages:

  • more instances of servlet engine running on server means more resources being used

  • i've never used jetty. don't think have tomcat-specific stuff going on in webapps, i'm not sure.

my main concern amount of resources jetty use. if had 1 tomcat instance running 4 webapps, difference in resources (memory/processor) 4 jetty instances running?

this question open-ended, i'm curious know if i'm overlooking or if has experience moving tomcat (embedded) jetty.

well think there no direct answer;

i might not understand ".deb" part i'm not debian freak :)

i prefer having instance of tomcat number of configurations aka catalina_home folders may specify apps , ports running, can have configs separately , change tomcat instance if needed.

also, see related post: jetty: embed or not embed?


Comments

Popular posts from this blog

apache - Add omitted ? to URLs -

redirect - bbPress Forum - rewrite to wwww.mysite prohibits login -

php - How can I stop spam on my custom forum/blog? -