Capacity is tight and running two full production stacks for blue-green is too expensive for the parks reservation API. Which deployment approach is most appropriate?
Select an answer to reveal the explanation.
Short Explanation
If you cannot afford two complete stages, do not rent the second theater — upgrade seats row by row instead. Rolling uses the capacity you already have and keeps service up. When dual-stack blue-green cost is the blocker, rolling (or sometimes in-place) is the practical fit.
Full Explanation
Blue-green requires roughly duplicate production capacity during the release window, which may be cost-prohibitive. Rolling deployments reuse the existing fleet by updating subsets gradually, preserving availability without a full parallel stack. Permanent idle twins and only big-bang outages do not solve the capacity constraint as effectively as batch rolling updates.