Tutorials Entity Framework Core Tutorial
Infrastructure Layer with EF Core
Infrastructure Layer with EF Core: free step-by-step lesson with examples, common mistakes, and interview tips — part of Entity Framework Core Tutorial on Toolliyo Academy.
On this page
Entity Framework Core Tutorial · Lesson 77 of 100
Infrastructure Layer with EF Core
Beginner ✓ → Intermediate ✓ → Advanced ✓ → Professional
Professional · 4 — Real projects · ~10 min · Module 8: Enterprise Architecture
What is this?
Infrastructure implements persistence — ShopNestDbContext, migrations, repository classes, DI registration — referencing EF Core packages Application avoids.
Why should you care?
ShopNest can integration-test Application with fake repositories while Infrastructure team owns SQL tuning and migrations.
See it live — copy this example
Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).
public static class DependencyInjection
{
public static IServiceCollection AddShopNestInfrastructure(
this IServiceCollection services, IConfiguration config)
{
services.AddDbContext<ShopNestDbContext>(o =>
o.UseSqlServer(config.GetConnectionString("ShopNest")));
services.AddScoped<IProductRepository, ProductRepository>();
services.AddScoped<IUnitOfWork, UnitOfWork>();
return services;
}
}What happened?
- Extension method registers DbContext and repositories.
- Api Program.cs calls AddShopNestInfrastructure — EF types confined to Infrastructure assembly.
Practice next
- Create Migrations folder in Infrastructure project.
- build all IRepository interfaces here.
- Export single AddInfrastructure extension from Infrastructure.
- Split read/write registration into AddShopNestReadInfrastructure.
- Add IDesignTimeDbContextFactory for migration CLI without startup Api.
Remember
Infrastructure owns EF Core and SQL concerns. DI extension wires DbContext and repos. Migrations live with DbContext project.
ShopNest infra module
New microservice references ShopNest.Infrastructure package and calls AddShopNestInfrastructure.
Outcome: Consistent EF setup across Order API and Catalog API.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!
