Parallel change
Parallel change is a migration technique that introduces a compatible replacement alongside an existing structure or interface, transitions use to the replacement, and then removes the old one.
Grokking Software Architecture
A database migration pattern that introduces compatible schema changes in stages so old and new application versions can operate during a rollout.
- How it is used
- Uses phased schema changes to keep services compatible during zero-downtime rollouts.
- How deep it goes
- Explains three migration phases, dual writes, backfills, and concurrency risks.
- Examples
- Uses a customer_phone-to-phone_mobile rename and an orders insert that writes both columns.
- What you can do after
- Operate a phased schema migration while old and new service versions remain active.
Read how Grokking Software Architecture explains parallel change →
Crack Any Codebase with AI
The expand-contract pattern changes a live schema in stages by adding compatible structures, migrating reads and writes, backfilling data, and later removing the old structures.
- How it is used
- Safely rolls out live schema changes without locking a busy table in one disruptive step.
- How deep it goes
- Details adding structures, dual-writing, backfilling, switching reads, and later removal, but not application endpoint tracing.
- Examples
- Uses replacement columns, duplicate credential fields, migration files, git commits, and GitHub's gh-ost.
- What you can do after
- Operate/configure staged schema rollouts and diagnose incomplete migrations from their history and duplicate structures.
Read how Crack Any Codebase with AI explains parallel change →
Also covered in
Related concepts
- canary deploymentused by · A canary deployment is a release strategy that exposes a change to a limited portion of users, traffic, or infrastructure before expanding it more broadly.
- inputuses · An input is information, a value, or an action supplied to a system, program, or computation for processing or to influence its behavior.
- schemauses · A data schema is a formal specification of the structure, fields, types, relationships, and constraints of data.
- backward compatibilityaddresses · Backward compatibility is the property of a newer or changed system remaining usable by existing clients, code, data, or integrations that depend on earlier interfaces or behavior.
- dual-write modehas part · Dual-write mode is a pattern in which each logical data update is written to two separate destinations or representations.
Questions about parallel change
What is parallel change?
Parallel change is a migration technique that introduces a compatible replacement alongside an existing structure or interface, transitions use to the replacement, and then removes the old one.
Which Manning books explain parallel change?
Grokking Software Architecture and Crack Any Codebase with AI.
What are the parts of parallel change?
Parallel change includes dual-write mode.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

