What is a migration in EF Core?
PICTURE THIS: DATABASE INDEX
Simple meaning
A migration is a versioned change to the database schema generated from the model.
WHY — EF Core instead of guessing?
Why interviewers care about EF Core:
people who only read docs from people who shipped.
and tied to .NET work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1A migration is a
versioned change to the database schema generated from the model.
- 2I apply it with
update-database or at deploy.
- 3Never edit production schema
only by hand if migrations own it.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
A migration is a versioned change to the database schema generated from the model. I apply it with update-database or at deploy.