MNW #028: Using Multiple EF Core DbContexts In a Single Application

Read time: 4 minutes

A big thank you to our sponsors who keep this newsletter free to the reader:

Today's issue is sponsored by Hasura, an open-source engine that gives instant GraphQL and REST APIs on new or existing SQL Server, enabling teams to ship apps faster.

And by Localizely, the translation management platform that helps you translate texts in your app for targeting multilingual markets. With Localizely you can:

collaborate with your team on translations
reduce errors and keep translations consistent
automate translation workflow with GitHub, GitLab, Figma and other integrations
order translations from professionals

Entity Framework Core (EF Core) is a popular ORM in .NET that allows you to work with SQL databases. EF Core uses a DbContext, which represents a session with the database and is responsible for tracking changes, performing database operations, and managing database connections.

It's common to have only one DbContext for the entire application.

But what if you need to have multiple DbContexts?

In this week's newsletter we're going to explore:

When you may want to use multiple DbContexts
How to create multiple DbContexts
What are the benefits of using multiple DbContexts

Why Use Multiple DbContexts?

There are a few cases where using multiple DbContexts can be useful.

Multiple Databases

Does your application need to work with multiple SQL databases? Then you're forced to use multiple DbContexts, each one dedicated to a specific SQL database.

Separating Concerns

If the application you're building has a complex domain model, you may see an improvement by separating concerns between a few DbContexts, where each one is responsible for a specific area of the domain model.

Modular Monolith

When you're building a Modular Monolith, using multiple DbContexts can be practical because you can configure a different database schema per DbContext, giving you logical separation at the database level.

Read Replicas

You can configure a separate DbContext instance to access the read replica of your database, and use that DbContext for read-only queries.

You can also configure QueryTrackingBehavior.NoTracking on the DbContext level to improve query performance.

Creating Multiple DbContexts In a Single Application

Here's how you can easily configure multiple DbContexts. Let's say we have a CatalogDbContext and an OrderDbContext in our application. We want to configure them using the following constraints:

Both DbContexts use the same database
Each DbContext has a separate database schema

First we need to configure the CatalogDbContext and OrderDbContext with the DI container. You can do this by calling the AddDbContext method and specifying which DbContext is being configured, and then using the SQL provider specific method to pass the connection string. In this case I'm connecting to SQL Server with the UseSqlServer method.

If you just want to use both DbContexts in the same schema, then this is all the configuration you need. You can now inject the DbContext instances in your application and use them.

However, if you want to configure a different schema for each DbContext then you also need to override the OnModelCreating method and specify the custom schema with HasDefaultSchema.

Limitations with multiple DbContexts:

It's not possible to do a join between different DbContext instances, because EF Core doesn't know if they are using the same database
Transactions will only work if the DbContexts are using the same database. You have to create a new transaction and share it between the DbContexts by calling the UseTransaction method

Migrations History Table

If you decide to use different schemas per DbContext, you will be unpleasantly surprised to learn that the default schema doesn't apply to the migrations history table.

You need to configure this by calling the MigrationsHistoryTable method and specifying the table name and schema where the migrations history for that context will live. I used the HistoryRepository.DefaultTableName constant in this example, but you can specify a custom table name if you want to.

Benefits Of Using Multiple DbContexts

Using multiple DbContexts can offer several benefits to your application:

Separation of concerns
Better performance
More control & improved security

Each DbContext can be responsible for a specific subset of the application's data, which can help organize the code and make it more modular.

When you separate data access into multiple DbContexts, the application can reduce the risk of contention and improve concurrency, and this can improve performance.

And if you're using multiple DbContexts, you can configure more granular access control to improve application security. You can also optimize performance and resource usage.

In Summary

Using multiple EF Core DbContexts in a single application is straightforward and has many benefits.

For ready-heavy applications you can configure a separate DbContext to turn off query tracking by default and get improved performance.

Also, using multiple DbContexts is practical if you're building a Modular monolith. You can configure the DbContexts to be in separate database schemas, giving you logical separation at the database level.

That's all for today.

See you next week.

Whenever you're ready, there are 3 ways I can help you 🔥

To access to all of the source code that I use in my YouTube videos support me on Patreon
For more practical & in-depth coding examples subscribe to my YouTube channel
Promote yourself to 11.000+ subscribers my sponsoring this newsletter (booked out 2 months)

P.S. I'm planning to release a paid course soon. I want you to help me decide on the topic. What would you like to learn?

You received this email because you subscribed to our list. You can unsubscribe at any time.

Dragise Cvetkovica 2, Niš, 18000, Serbia

professionals Entity Framework Core Multiple EF Core DbContexts translation management platform consistentautomate translation workflow existing SQL Server other integrationsorder translations

MNW #028: Using Multiple EF Core DbContexts In a Single Application

MNW #028: Using Multiple EF Core DbContexts In a Single Application

Why Use Multiple DbContexts?

Creating Multiple DbContexts In a Single Application

Benefits Of Using Multiple DbContexts

In Summary

Key phrases

Older messages

MNW #027: How To Apply Functional Programming In C#

MNW #026: Outbox Pattern For Reliable Microservices Messaging 📦

Milan's .NET Weekly Newsletter And You 🎁

MNW #024: Messaging Made Easy With Azure Service Bus

Invitation - Modular Monoliths: How To Build One & Lessons Learned 🔥

You Might Also Like

Edge 387: Tool Learning in Autonomous Agents

Tesla layoffs 🚗, OpenAI Batch API 🤖, tech jobs leaving California 💼

Introducing our new mobile app! 🥁📱

BetterDev #256 - How to write a code formatter and a search engine in 80 lines of Python

New Blogs on ThomasMaurer.ch for 04/16/2024

April TC39 meeting; Rspack v0.6; future of JS packages; Evan You on Vue, Vite, etc.

Ingesting & Using CAD Data for Real-Time 3D

It’s Easy. But Is It Easy Enough? 🤓

Re: Free Class: Master the Notes app

Two Tesla execs leave amid layoffs