Migrate a breaking analytics schema change
Source: interviewintermediate
WHAT IT TESTS: safe rollout of a breaking data contract. OUTLINE: dual-write both fields during overlap, backfill history, migrate consumers, then deprecate the old field.
WHAT IT TESTS: whether you can evolve a data contract without breaking downstream consumers. ANSWER OUTLINE: version the schema, dual-write project_id and workspace_id during a transition window so old and new consumers both work, backfill historical events so the new field exists across the full range queries need, migrate dashboards and experiments to the new field, then deprecate and remove the old one.
Read the original → interview
- #schema-migration
- #analytics
- #dual-write
- #backfill
- #data-contracts
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.