All right. 1
See the next question. 2
Hill says right now I run five different war files and Jay boss when I which I then connect to Postgres 3
database is on some server I am looking at compose actually going through that course at the moment 4
to set it up. 5
The question I have is should I create multiple J Bos containers with compose or just continue running 6
all five in one in production we have five different J servers 7
so 8
I would say try both. 9
If you have five different war files and J boss without being a Java expert I mean you're the Java guy. 10
What do you think. 11
Yeah I can talk a little bit into this anyways. 12
So my recommendation is it's typically been all right don't don't boil the ocean and Bret says this 13
often fancy do what you're already comfortable with do what you already know. 14
If that's where you have lots of tooling and everything around we've got a single J Bar server that 15
has lots of war files in it and we know how to work with that we know how to instrument it and everything. 16
Great to get that containerized and start working from there. 17
Personally I'm a fan of splitting that out into multiple containers and so that would probably be a 18
long term approach because I imagine for the most part your if you update one do you need to redeploy 19
the other four. 20
And so if they're all in separate containers you can deploy one you can roll out updates to one without 21
having to bring down the others. 22
They're all independent from each other. 23
Yes that means you have additional overhead you're now running five day Vos servers instead of just 24
one but I think at the end of the day there's not that much difference. 25
I mean the jailhouse application server sure does have some overhead but I would and again I don't know 26
your app at least in my experience the amount of overhead from the application server in comparison 27
to the app itself is quite low that most of the CPU memory utilization all that stuff is coming from 28
the app not from the server itself so running multiple instances of J Bos probably using it to hurt 29
you. 30
But again I don't know your your exact situation too. 31
Yeah and I think that you know getting getting server resources for that is probably easier. 32
Probably less of an issue than the fact the game the abilities you gain by having the flexibility right 33
like you can have scale one without scaling the others you can replace one without replacing the others. 34
I think this is in general this question is very similar right to other questions we get about a couple 35
a couple weeks ago we had people asking well if I have a bunch of Apache Web sites should I run them 36
all in Apache virtual servers or should I split them out in the separate containers and my answer was 37
very similar to yours Michael that I would have video that it all would work in one but eventually I 38
would be splitting the mountain separate containers because containers provide that level of isolation 39
and artifacts. 40
That gives me the flexibility for distributed computing where I can you know we can't really ever get 41
to and to micro services and this necessary it doesn't mean that your boss is micro servers yet but 42
you know to me there is there's a there's a wide array of size of applications and as we start splitting 43
things up or making different you know applications that run separately whether it's a war file or something 44
else. 45
The more we split these and isolate these things out generally the more flexibility the easier it is 46
to get uptime the easier it is to troubleshoot it. 47
It's not perfect then not everything is better right. 48
You have sometimes duplication of effort you end up with more things you've got to manage. 49
You got maybe a little bit harder network troubleshooting depending on how your apps work it might affect 50
performance if they're across the network instead of in the same machine. 51
So there's lots of things to consider but in general we're all evolving into a way where we're splitting 52
things out more and more and more when it makes sense. 53
And yeah and from my experience too. 54
Again this may not be your experience or it's going on here. 55
But know we've had several Tomcat containers or a tomcat servers that had lots of war files in it and 56
we simply did that because it was convenient at the time to spin up a new machine dish up the new Tomcat 57
and since all that stuff was it was a lot of overhead in the past and so it's fine I don't want to do 58
that I'm just going to deploy another war files so this other one it's already running it's good enough 59
and so that was more to reduce the OPs overhead and the amount of time to speed things up but now as 60
you become more familiar with containers and everything that overhead doesn't really exist anymore because 61
now it's early in the process you're building these container images and it's easier to spend things 62
up. 63
So yeah that's yeah it is a good question. 64
Yeah I mean we get the same question about databases should I put all of my databases into one my sequel 65
server or should I have multiple my sequel containers and I would say this depends. 66
What is your motivation that the cheapest thing to do is to put them all in one because it's lower memory 67
overhead. 68
It's you know probably a little less redundancy in on in terms of the necessary things you need to run 69
but most of us are splitting things out when we can in order to gain flexibility. 70
Really.