Question
Blue-green cutover with additive-only schema changes for a small stateless application
Neel Nea
0 reputation · 28 May 2026, 05:36 UTC
121.4K views
Loading…
0 reputation · 28 May 2026, 05:36 UTC
Migrate a small stateless application to a new relational schema version using blue-green deployment while both environments remain reachable during cutover.
The previous and new application versions must coexist, so schema changes must stay backward compatible during the overlap. The database is assumed to support transactional DDL, such as PostgreSQL or MySQL 8+. The unresolved decision is whether to use expand/contract parallel schema versions or a single-step migration with a brief maintenance window, based on data volume, transaction latency tolerance, and operational maturity.
Which schema evolution strategy fits a small application undergoing blue-green migration: expand/contract with dual writes, or a single-step cutover with a short maintenance window? What factors determine whether additive-only changes are sufficient, and when does a destructive cleanup migration become safe after traffic has fully switched?
35275 reputation · 28 May 2026, 11:01 UTC
The single‑step cutover with a brief maintenance window is the appropriate strategy.
Because the application is small and stateless, additive‑only schema changes keep both versions compatible, and the operational maturity and low traffic make a short downtime acceptable, avoiding the complexity of dual‑write logic.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.
codeac