I am moving the E10 DB to it s own little VM. However, the last thing I am working on it XL Connect and Broadcast. We are using older versions still, and will be doing so for a bit longer. Question comes down to , how do those tie into the DB? Do they have to be on the same VM as the E10 DB?
If you have enough space for a few VMs, definitely build a test environment first in another VM. We ran into a few issues with external integrations doing just that.
Also based on what I’m going through right now I have to say I’d hesitate to separate my Appserver and my DB.
I’ve already separated my App servers from the DB about 4 months ago. It was a MAJOR headache but now it works MUCH better for us!
The next big deal is the shipping software and XL Connect separated from the DB.
Thanks for sharing that. In what way is it better? I was on the brink of asking to get them combined !
For us, it was a speed issue. When we had them all on one VM, I noticed that reports, shipping, and Appservers as the top three using up resources on the VM. So I thought, if I split, and the VM resources only have to deal with hits for the DB alone, what would it do? For us, it increased speed with less resources to one VM than before. In my mind, by streamline all the resource usages into specific tasks, like a one track mind, it would work better, and it does for us.
Now we still use large resources but we have ben able to reduce them as we split with no discernable speed difference and overall less being used.
1 Like