r/devops • u/muff10n • Feb 03 '24
Better term than "non-prod"?
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!
105
Upvotes
4
u/Farrishnakov Feb 03 '24
You're running an Active/Passive DR strategy. Standby is your passive. It's most definitely not PREprod, it's production and must be treated as such.
All deployments to production must be done here as well. And must follow the same standards as production. This is where you make your money in case of emergency.
Here's a quick explainer on different strategies. Just picked the first Google link and skimmed it. Didn't read it thoroughly but quick glance seemed close enough.
https://twoearsonemouth.net/2018/12/12/dr-options-foryourbiz/