👀 Views: 72 💬 Answers: 1 📅 Created: 2025-06-05

Entity Framework ASP.NET Core Database C#

I'm updating my dependencies and I've searched everywhere and can't find a clear answer... Hey everyone, I'm running into an issue that's driving me crazy. I'm currently developing a .NET 6 Web API that manages multiple entities using Entity Framework Core. For separation of concerns, I've set up two different `DbContext` classes: `UserDbContext` and `ProductDbContext`. However, I'm running into performance bottlenecks that seem to relate to connection pooling, especially when making simultaneous requests to both contexts. I'm seeing this warning in the logs: `A connection is already open and need to be opened again.`, which is especially prevalent under load. Here's how I'm setting up my `DbContexts` in the `Startup.cs`: ```csharp services.AddDbContext<UserDbContext>(options => options.UseSqlServer(Configuration.GetConnectionString("UserDatabase"))); services.AddDbContext<ProductDbContext>(options => options.UseSqlServer(Configuration.GetConnectionString("ProductDatabase"))); ``` When I make calls to both `DbContexts` in parallel from my controllers, like so: ```csharp public class UserController : ControllerBase { private readonly UserDbContext _userContext; private readonly ProductDbContext _productContext; public UserController(UserDbContext userContext, ProductDbContext productContext) { _userContext = userContext; _productContext = productContext; } [HttpGet] public async Task<IActionResult> GetUserAndProducts(int userId) { var user = await _userContext.Users.FindAsync(userId); var products = await _productContext.Products.ToListAsync(); return Ok(new { user, products }); } } ``` I have tried increasing the `Max Pool Size` in the connection string and also implemented `await` for asynchronous operations to avoid blocking calls. However, the scenario continues, and I'm not sure if the question lies within the way I’m managing the scopes of these `DbContexts` or the actual database operations themselves. Any insights on best practices for handling multiple `DbContexts` effectively, or tips on optimizing connection pooling in this scenario would be greatly appreciated. For context: I'm using C# on Linux. Am I missing something obvious? I'd really appreciate any guidance on this. I'm developing on Ubuntu 20.04 with C#. Hoping someone can shed some light on this. My development environment is CentOS.