Are you using multiple DEV and PROD instances? If yes, what is your use case?

[Suggy]

Are you using multiple DEV and PROD instances? If yes, what is your use case?

PS - This question is for information purpose only. If you have come across such a situation, do share the details so that any other user looking for details on this topic would get some idea/details.

Thanks in advance!

[scottl]

I'd say you'd only need to have multiple DEV environments for individual large projects, with different dev teams (previous experience). And multiple PROD environments for a large user count hitting the servers, like a public facing SN Portal (built many). Outside of that unsure, others may share other insights.   

[TryciaK]

Yes, we are using multiple DEV (Development) and PROD (Production) instances to maintain a clear separation between testing and live environments. The DEV instances are primarily used for developing new features, testing configurations, performing code reviews, and debugging any issues without impacting end users. Once features are thoroughly tested and approved in DE

[Ehab Pilloor]

Hi @Suggy,

Yes, multiple sub production environments are used by many organizations, one to configure, one for user acceptance testing and one for client testing to see whether it is working as per requirements.

Regards,

Ehab Pilloor

[Dr Atul G- LNG]

Hi @Suggy 

I had a similar experience with one of my previous telecom clients. We had three development instances and one production instance.

The reason for this setup was that the client’s development environment was quite large, and they preferred to keep the three major development streams on separate instances. We treated the third development instance as the "master", where all code changes from the other two dev instances were consolidated.

From this master dev instance, the code would then be promoted to Test → UAT → Production.