After green proves healthy for the licensing portal, blue is kept briefly as instant rollback capacity and then recycled. Which practice does this describe?
Select an answer to reveal the explanation.
Short Explanation
Blue-green is a handoff dance: prove green, flip traffic, keep blue warm for a bit in case you need to flip back, then reclaim the old stack so you are not paying forever. That validate–switch–retain–recycle loop is the blue-green lifecycle in a nutshell.
Full Explanation
After a successful blue-green cutover, teams commonly retain the previous environment for a short rollback window, then recycle its capacity to control cost. That lifecycle — validate, switch, retain briefly, reclaim — is core blue-green operations. Canary does not center on a full idle twin; never reclaiming blue wastes spend; in-place has no parallel environment to retain.