Best deployment strategy for PlayFramework applications?

Viewed 5619

This question is server oriented. I have a hosted server (a rather small one, 1,6Ghz atom, 2Go, 200 GO) with a couple (4 or 5) play apps and more coming. Most of these apps have a real small usage, let's say a hundred requests a day each.

  1. Is it better to deploy each of those applications using the embedded server of Play! and thus use 64mb of memory for each application?

  2. Or deploy a Tomcat with all the applications inside the tomcat? With a bigger memory shared by all the apps?

EDIT :

I'll add a little further information about my situation. The server also hosts :

  • About 10,15 PHP websites on Apache2
  • A SVN server going through Apache mod_dav_svn
  • A tomcat used for Sonar
  • A standalone installation of Jenkins (via Jetty)

My original plan was to deploy all these stuff in Tomcat. Having the apps, Sonar & Jenkins running on Tomcat and Apache2 for static ressources. (Images, scripts)

COMMENT

Last point, I'm aware that having Sonar & Jenkins, Continuous integration systems on a production environment isn't really optimal. But since these are only running at night (automated builds) they are not overloading the system. Plus I'm a student, financially an additional "CI/build" server is out of my financial capacities.

3 Answers
Related