Should the Central Instance be separated from the DB Server?

[Former Member]

I am planning for a distributed ECC system. I plan to have multiple Dialog Instances. I am trying to determine whether or not I want to install the Central Instance on the same system as the Database. I am using a virtualized environment, so I am not concerned with the network between the two systems. I have been told by my VAR that it is recommended to separate the DB server and the CI but I don't see why. Knowing that the CI talks directly to the DB, why wouldn't you want to keep them together? I am adding this post to find out what others are doing and what they recommend.

[Former Member · Accepted solution]

Will your VM's be spread across multiple systems? If you are running these across just one or two systems then it may not make sense to split the CI from the DB since you are not distributing the load. Of course, when you do split these it does give you the chance to scale across multiple VM host systems in the future.

[Former Member · Accepted solution]

They will be spread across two physical systems.

We have made the decision to create the Central System. We actually ran into some issues with our BSI application. It was not able to calculate taxes correctly in the Distributed system. Also, we feel we have ample CPU and memory and combining the two systems should not cause any hardware bottlenecks. We also chose this design in order to free up more hardware resources for Dialog Instances. With the added Dialog instances, we can prevent users from logging on directly to the Central Instance.

[Former Member · Accepted solution]

That sounds like a good plan. I have seen that done before where users are directed toward dialog servers and the CI is setup only for admin access and background processing.