This is a very useful guide. I'd add one additional step that can sometimes be useful if you're doing a more complex change than adding a field to an object. For example, sometimes you may want to read from an entirely new schema or data source, while ensuring that the user-facing behavior stays the same.
In that case, you'd want to add a step between steps 2 and 3 where you double-read, either inline or within a shadow workload, and add telemetry to alert you if there are discrepancies between the two versions.
Only when you're confident that the two data models are producing acceptably equivalent results would you cut over the primary reads to the new model.
This pattern often comes to play when you break off a piece of state from a monolithic database into a dedicated service.
In that case, you'd want to add a step between steps 2 and 3 where you double-read, either inline or within a shadow workload, and add telemetry to alert you if there are discrepancies between the two versions.
Only when you're confident that the two data models are producing acceptably equivalent results would you cut over the primary reads to the new model.
This pattern often comes to play when you break off a piece of state from a monolithic database into a dedicated service.