@Jens Knobloch -
If it's production and exposed to the internet I'd go with option A if you have the hardware readily available. If not, then option C would be my choice (and what we do here at CCC, mostly).
Cons for same server
- every upgrade will introduce the possibility of outage on the product not being upgraded
- Server has hardware problem both apps are down
- can be more difficult to trace performance problems with multiple servers on board
- I always front my atlassian software with Apache supplying the SSL security so with apache 2.4.2 and named virtual hosts combined with SSL you have to give each software app a different IP address - which while you can do this and have it work on a single system it's a real pita
Pros for same server
- if something goes wrong with either app you know what server to go investigate
- you only need to have staging server to practice your upgrades on
- there's other bonuses but for a production environment separate VM's is the way to go even though that means you'll be duplicating software (apache, tomcat at least, postgresql if you're going to use the right database)
this answer feels incomplete to me .... probably because it's shorter than my preferred 30 page length (tongue in cheek). but hey, let me know how it reads.
-wc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.