Entity Framework Core service default lifetime

by

Yes, the default life time for DbContext is scoped. This is intended this way.

Instantiating DbContext is pretty cheap and it makes sure that the your do not use to many resources. If you’d have a DbContext with a singleton lifetime, then all records that you read once will be tracked by the DbContext, unless you specifically disable tracking. This will require much more memory usage and it will keep growing.

And the more the DbContext tracks, the lower the performance will be. That’s why you often see DbContext only used within a using(var context = new AppDbContext()) block.

In web applications however, using the using block is bad, because the lifetime is managed by the framework and if you dispose it to early the calls after that will fail with an exception.

If you use transient lifetime on the other side, you will lose the “transaction” functionality. With scoped, the DbContext has a transaction scope that’s as long as the request.

If you need more fine-grained control, you have to use the Unit of Work pattern (which DbContext already kind of utilize).

For your second question:

If you create a service, it must have a lifetime that’s equal to the one of the scope or shorter (read: Scoped or transient).

If you explicitly need a longer life-time for a service, you should inject a DbContext factory service or factory method into your service.

You can accomplish this with something like 

services.AddTransient<Func<AppDbContext>>( (provider) => new Func<MyDbContext>( () => new AppDbContext()));
services.AddSingleton<IMySingletonService, MySingletonService>();

And your service may look like this: 

public class MySingletonService : IMySingletonService, IDisposable
{
    private readonly AppDbContext context;

    public MySingletonService(Func<AppDbContext> contextFactory)
    {
        if(contextFactory == null)
            throw new ArgumentNullException(nameof(contextFactory));

        // it creates an transient factory, make sure to dispose it in `Dispose()` method.
        // Since it's member of the MySingletonService, it's lifetime
        // is effectively bound to it. 
        context = contextFactory();
    }
}

More Related Contents:

  1. How to run stored procedures in Entity Framework Core?
  2. why remove-migration run my app?
  3. How to update the model when using database first approach
  4. AddDbContext or AddDbContextPool
  5. Entity Framework Core: DbContextOptionsBuilder does not contain a definition for ‘usesqlserver’ and no extension method ‘usesqlserver’
  6. where to download the dotnet-dev-win-x86.1.0.0-preview 2-1-003180
  7. Dynamically change connection string in Asp.Net Core
  8. Where are the Login and Register pages in an AspNet Core scaffolded app?
  9. How to instantiate a DbContext in EF Core
  10. Unable to create migrations after upgrading to ASP.NET Core 2.0
  11. Dynamically changing schema in Entity Framework Core
  12. EF CORE 2.1 HasConversion on all properties of type datetime
  13. Equivalent for .HasOptional in Entity Framework Core 1 (EF7)
  14. .NET Core vs ASP.NET Core
  15. How to set redirect_uri protocol to HTTPS in Azure Web Apps
  16. ASP.NET Core change EF connection string when user logs in
  17. Using EF Core ThenInclude() on Junction tables
  18. Unable to edit db entries using EFCore, EntityState.Modified: “Database operation expected to affect 1 row(s) but actually affected 0 row(s).”
  19. .Net Core on Raspberry Pi 4 with Raspbian?
  20. Add migration with different assembly
  21. Entity Framework Core: `SqlNullValueException: Data is Null.` How to troubleshoot?
  22. How to publish environment specific appsettings in .Net core app?
  23. What goes into DbContextOptions when invoking a new DbContext?
  24. Configure cors to allow all subdomains using ASP.NET Core (Asp.net 5, MVC6, VNext)
  25. Read request body twice
  26. How to get user information in DbContext using Net Core
  27. How should I manage DbContext Lifetime in MVC Core?
  28. How to inject a reference to a specific IHostedService implementation?
  29. Store / Retrieve ConnectionString from appSettings.json in ASP.net Core 2 MVC app
  30. Update-Database command is not working in ASP.Net Core / Entity Framework Core because object in database already exists

Leave a Comment