3 ms·
Tomcat deployment is also pretty easy, can package a war file and then there are even context parameters if you want to use the same war for multiple instances.
by amalag 14y ago
Tomcat deployment is also pretty easy, can package a war file and then there are even context parameters if you want to use the same war for multiple instances. That being said this is a nice option which is already integrated with apache or nginx so don't have to setup a proxy, and this will handle static assets automatically if you are not using a CDN.
- FooBarWidget 14y agoYep. Coming from a different background, Phusion Passenger is not as J2EE-ish as the other Java app servers. We do things a bit differently, for example: - We don't run multiple apps inside the same JVM. We strictly run each app in its own JVM, no exceptions. As I've understood, running multiple apps in the same JVM can cause garbage to leave behind when you try to uninstall an app. And the JVM does not always perform optimally when the heap is large. - We integrate directly into Apache and Nginx, so no need to setup AJP reverse proxies. I don't think Nginx has an AJP connector. - Phusion Passenger is also a great option for people who want to take advantage of JRuby (whether it's for the speed, or the threading implementation, or whatever) but aren't intimately familiar with the J2EE stack. - Our support for multiple Ruby versions (and even multiple languages) allows you to easily mix and match things. No need to commit 100% to Java, or MRI, or any particular implementation/version.