How would you explain the correct lifetime for EF Core DbContext in an ASP.NET Core API?

How should DbContext lifetime be handled in ASP.NET Core APIs?

Explains DbContext lifetime and unit-of-work boundaries with practical .NET data-access examples and production trade-offs.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I usually treat DbContext as a scoped dependency in an ASP.NET Core API. One context instance is created for the request scope and used as a unit of work for that request. It tracks loaded entities, builds changes, and saves them with SaveChangesAsync. I would not register it as a singleton because it is not thread-safe and it can accidentally share tracked state across users or requests.

Full answer below

Practice focus

Understanding of DbContext lifetime and unit-of-work boundaries, EF Core/SQL behavior, API boundaries, production risks, and practical debugging or design judgment.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this matters
DbContext lifetime defines which changes belong to one unit of work and whether EF Core's non-thread-safe state stays inside one request. A poor boundary can mix unrelated work, retain tracked entities, or create concurrency failures.
I usually treat DbContext as a scoped dependency in an ASP.NET Core API. One context instance is created for the request scope and used as a unit of work for that request. It tracks loaded entities, builds changes, and saves them with SaveChangesAsync. I would not register it as a singleton because it is not thread-safe and it can accidentally share tracked state across users or requests.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
A scoped DbContext works well when an endpoint reads or modifies a small set of related data and saves once. For example, an order update can load the order, apply a status change, add an audit entry, and save in one request scope. The trade-off is that long-running jobs or parallel workloads should not keep reusing the same context. For background processing, I create a new scope or use per unit of work.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Treating DbContext lifetime and unit-of-work boundaries as a syntax detail instead of a production behavior.
Not checking generated SQL, query plans, or actual data volume.
Testing only with tiny local data and assuming production will behave the same.
Fixing symptoms with caching, timeouts, or retries before understanding the data-access cause.

How would you explain the correct lifetime for EF Core DbContext in an ASP.NET Core API?

Practice focus

Answer path

Why this matters

Review signals

Coding practice

Follow-up prompts

Continue practice

Tech stacks

Skill areas

Suggest an improvement