Deploy to web container, bundle web container or embed web container...
- by Jason
I am developing an application that needs to be as simple as possible to install for the end user. While the end users will likely be experience Linux users (or sales engineers), they don't really know anything about Tomcat, Jetty, etc, nor do I think they should.
So I see 3 ways to deploy our applications. I should also state that this is the first app that I have had to deploy that had a web interface, so I haven't really faced this question before.
First is to deploy the application into an existing web container. Since we only deploy to Suse or RedHat this seems easy enough to do. However, we're not big on the idea of multiple apps running in one web container. It makes it harder to take down just one app.
The next option is to just bundle Tomcat or Jetty and have the startup/shutdown scripts launch our bundled web container.
Or 3rd, embed.. This will probably provide the same user experience as the second option.
I'm curious what others do when faced with this problem to make it as fool proof as possible on the end user.
I've almost ruled out deploying into an existing web container as we often like to set per application resource limits and CPU affinity, which I believe would affect all apps deployed into a web container/app server and not just a specific application.
Thank you.
