IIS Environment Setup

dj · Post by dj » Tue May 24, 2016 9:32 am

Hi All,

We are preparing a high level environment setup and would like to get your valuable suggestions. looking for different approaches we are trying to figure it out.

DEV and ST(System Testing) Setup:

Design 1: To setup the DEV and ST in Same Server.

cons: If one of the env is down , will not affect the other?
Any other space/cpu processing constraints to be consider

Design 2: In 2 different Separate Physical Servers.
Except the Cost, are there any constraints to this approach.

Thanks

PaulVL · Post by **PaulVL** » Tue May 24, 2016 10:42 am

Sounds a lot like you could use the help of a good consultant. People actually get paid for this stuff and knowledge transfer.

There is a LOT of things to consider when planning your new environment. It's not a short conversation.

ray.wurlod · Post by **ray.wurlod** » Tue May 24, 2016 5:26 pm

One definite con for the "same server" approach, which a couple of my clients encountered, is that all development has to stop if any heavy duty testing (such as performance testing) is contemplated. They committed the additional booboo of underconfiguring their non-production environment.

qt_ky · Post by **qt_ky** » Wed May 25, 2016 4:58 am

If you go with design 2 and you have any "per install" licenses for add-on modules such as QualityStage USAC or AVI, then it also costs more for those items.