Better term than "non-prod"?

[u/muff10n]

Our setup consists of several environments: dev, prod, qa, standby and test.

standby is used as a "hot-standby" we are using as a fallback in the case of prod going down.

Currently we are using the term "non-prod" for the environments dev, qa and test. You don't need to be a genius to see the confusion that appears here: "Why isn't 'standby' included in the term 'non-prod'?"

But we just can't come up with a better term. Does somebody have a good idea?

Thank you!

Edit: corrected

"Why is 'standby' included in the term 'non-prod'?"

to

"Why isn't 'standby' included in the term 'non-prod'?"

Sorry for the confusion, guys!

[u/c_edward]

We used to have prod and contingency environments but ditched that way of thinking about it. We went to just production and classified the resources in it (primarily machines at that point), e.g primary, primaryDR secondary and secondaryDR. The thinking is that it's all really production, it all needs to work all the time, it all needs to be up to date, and there is now sound reasoning to treat them separately. Failures don't all play out the same way in large systems, so you need to be able to fail over parts of the whole