Multiple ChoiceBeginner 45s
Parallel Change for APIs
The parallel change (expand-contract) pattern for an API change proceeds as:
Options
- 1Contract first by removing the old field, then expand by adding the new one after consumers migrate
- 2Replace the endpoint atomically in a single deploy so no intermediate incompatible state exists
- 3Expand by adding the new field, migrate consumers, then contract by removing the old field
- 4Keep both the old and new versions of the field forever without ever planning any deprecation
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.