An internal low-risk municipal wiki can accept brief downtime, but tax-filing-week services cannot. How should deployment strategies differ?
Select an answer to reveal the explanation.
Short Explanation
Match the parachute to the jump. A quiet internal wiki can stomach an all-at-once bump; tax week needs rolling or blue/green so citizens keep filing while you ship.
Full Explanation
Deployment strategy should match business risk: all-at-once may be acceptable for low-impact internal apps, whereas high-stakes seasonal services need rolling or blue/green to limit downtime. Inverting risk controls, year-long freezes, or identical risky cutovers for both classes ignore availability requirements.