UAT and Production environment in the same platform

[Mad_1]

Your view and experience was sought on the captioned subject.

Thanks.

[Steve Lewis · Accepted solution]

If a program in UAT causes a server panic then that will crash your production system. I am sure that lawyers will argue the possibility of that happening regardless of how unlikely you think it is.

It doesn't allow you to test new patches in a UAT environment before Production.

If your UAT environment is load/stress tested, that will take performance away from production (cpu and i/o).

There may be a danger of accidentally running a production script in UAT (it happened to us). This means that your UAT environment has to be changed to make it not quite the same as production - which increases risk of not properly testing things.

Ideally your production environment should be well away from test areas and preferrably on a different lan.

Its what they do in my company and haven't changed it regardless of my worries/arguments. Its simply the way they have always done things.

[Paul_481]

Hi,

It is advisable and common practice in our company to separte the UAT and production. Most of our production servers requires almost 100% uptime.

In a UAT environment were testings are done, most of the time we might need to reboot our servers due to changes in parameters or patch upgrade. This will not be possible if UAT and production are on the same servers.

Regards,
Paul

[Mad_1]

The reason why UAT running with Production is cost implication, especially software license cost.

We have to balance cost against security, technical and operation implication.

Does anyone know there is any published recommendation / best practice from recognised organization on this topic?

Thanks.