How do you manage an event schema change?
This tests your understanding of data contracts and backward compatibility. A great answer details a phased, backward-compatible rollout (add nullable field), starting with consumers (warehouse) then producers, and mentions using a schema registry for…
This question tests your understanding of data systems as a whole, not just a database. It's about managing schemas as contracts and ensuring backward compatibility. A strong answer outlines a phased rollout: first, update consumers like the data warehouse to accept a new nullable field; second, update producers to send it; and third, use a schema registry to enforce versions. A red flag is focusing only on the `ALTER TABLE` command, ignoring the rest of the pipeline.
Read the original → branchboston.com
- #data engineering
- #schema evolution
- #system design
- #analytics
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.