Dependency Injection in ASP.NET Core — Complete Guide

Introduction

Dependency Injection in ASP.NET Core — Complete Guide is essential for .NET architects building ShopNest Enterprise Architecture Platform — Toolliyo's 69-article design patterns master path covering GoF creational, structural, and behavioral patterns; enterprise patterns (Repository, CQRS, Saga, Outbox); microservices; ASP.NET Core architecture; and senior interview prep. Every article includes minimum two mandatory real-world examples.

In Indian delivery projects (TCS, Infosys, Wipro), interviewers expect dependency injection with real banking, e-commerce, or SaaS examples — not toy animal demos. This article delivers production depth on Distributed Events.

After this article you will

• Explain Dependency Injection in plain English and in enterprise architecture terms
• Implement Dependency Injection in ShopNest Enterprise Architecture (Distributed Events)
• Compare anti-pattern vs production-ready pattern implementation
• Answer fresher and senior design pattern interview questions confidently
• Connect this lesson to Article 61 and the 69-article Design Patterns roadmap

Prerequisites

• Software: .NET 10 SDK, VS 2022 or VS Code, xUnit + Moq
• Knowledge: C# basics, SOLID principles
• Previous: Article 59 — Pipeline Pattern in ASP.NET Core — Complete Guide
• Time: 28 min reading + 30–45 min hands-on

Concept deep-dive

Level 1 — Analogy

Dependency Injection on ShopNest Enterprise Architecture is a proven blueprint for the Dependency Injection problem in growing platforms.

Level 2 — Technical

Dependency Injection applies ASP.NET Core idioms on ShopNest — middleware pipeline, IOptions configuration, background workers, and slice-based feature folders.

Level 3 — Architecture placement

[Client / API Gateway]
       ▼
[Application Layer — Handlers, Strategies, Commands]
       ▼
[Domain Layer — Entities, Domain Events, Specifications]
       ▼
[Infrastructure — EF Core, Message Bus, Polly, Cache]
       ▼
[Pattern Registration — Program.cs DI lifetimes]
       ▼
[xUnit + Moq — pattern behavior isolated]

Project structure

ShopNest.EnterpriseArchitecture/
├── ShopNest.Domain/           ← Entities, domain events, interfaces
├── ShopNest.Application/      ← Commands, queries, handlers (MediatR)
├── ShopNest.Infrastructure/   ← EF Core, Redis, RabbitMQ, Polly
├── ShopNest.Api/              ← ASP.NET Core Web API + Minimal APIs
├── ShopNest.Workers/          ← Hosted services, outbox processors
└── ShopNest.Gateway/          ← YARP API Gateway

Hands-on implementation — Distributed Events

Implement Dependency Injection in C# for Distributed Events: write a class or method, compile, and verify with a console or unit test.

1. Open a console or class library project.
2. Implement the concept in a focused class or method.
3. Add null checks and meaningful exception messages.
4. Run dotnet build and dotnet test.
5. Review naming and SOLID boundaries.

Anti-pattern (god class, swallowed exceptions, magic strings)

// ❌ BAD — no pattern, tight coupling, untestable
public class OrderController : ControllerBase {
    public IActionResult Place(OrderDto dto) {
        var conn = new SqlConnection("Server=.;...");
        // direct SQL, no repository, no UoW, no error handling
        return Ok();
    }
}

Production-style C# code

// ✅ CORRECT — Dependency Injection on ShopNest (Distributed Events)
public sealed class PlaceOrderHandler(
    IOrderRepository repo,
    IUnitOfWork uow,
    IPublisher events) : IRequestHandler<PlaceOrderCommand, Result<int>>
{
    public async Task<Result<int>> Handle(PlaceOrderCommand cmd, CancellationToken ct) {
        var order = Order.Create(cmd.CustomerId, cmd.Lines);
        await repo.AddAsync(order, ct);
        await events.Publish(new OrderPlacedEvent(order.Id), ct);
        await uow.SaveChangesAsync(ct);
        return Result.Success(order.Id);
    }
}

Complete example

// DependencyInjection — ASP.NET Core on ShopNest
builder.Services.AddScoped<IDependencyInjectionService, DependencyInjectionService>();

Real-World Example 1 — SaaS Multi-Tenant Platform

MANDATORY: Enterprise-grade Dependency Injection in ASP.NET Core implementation in a production saas multi-tenant platform.

Business requirement

Thousands of tenant organizations share infrastructure but require data isolation, per-tenant configuration, and independent billing.

Why Dependency Injection in ASP.NET Core is needed

Without Dependency Injection in ASP.NET Core, the SaaS Multi-Tenant Platform team at ShopNest faces tight coupling, untestable code, and painful refactors every sprint. Dependency Injection in ASP.NET Core decouples responsibilities so the Distributed Events module can evolve independently while meeting scalability and compliance requirements.

Architecture

[Client/API] → [Dependency Injection in ASP.NET Core Abstraction]
  → [ShopNest.Distributed Events Service] → [EF Core / Redis / Message Bus]
  → [Downstream: Audit, Notifications, Reporting]

Tech stack: ASP.NET Core, EF Core global query filters, Options pattern, API Gateway with YARP

Full working code

// REAL-WORLD EXAMPLE 1: SaaS Multi-Tenant Platform
// ShopNest Enterprise Architecture — Distributed Events module
// Pattern: Dependency Injection in ASP.NET Core

namespace ShopNest.Architecture.DistributedEvents;

public interface IDependencyInjectioninASP.NETCoreService
{
    Task ExecuteAsync(DependencyInjectioninASP.NETCoreRequest request, CancellationToken ct = default);
}

public sealed class SaaSMulti-TenantPlatformDependencyInjectioninASP.NETCoreService : IDependencyInjectioninASP.NETCoreService
{
    private readonly ILogger _logger;

    public SaaSMulti-TenantPlatformDependencyInjectioninASP.NETCoreService(ILogger logger)
        => _logger = logger;

    public async Task ExecuteAsync(DependencyInjectioninASP.NETCoreRequest request, CancellationToken ct)
    {
        _logger.LogInformation("[Dependency Injection in ASP.NET Core] Processing {Domain} request {Id}",
            "SaaS Multi-Tenant Platform", request.Id);

        // Production implementation — see Program.cs for DI registration
        await Task.Delay(10, ct);
        return Result.Success(request.Id);
    }
}

// Register in Program.cs:
// builder.Services.AddScoped();

Benefits achieved

• Loose coupling — swap implementations without changing controllers
• Unit testable — mock IDependencyService in xUnit tests
• Scalable — horizontal scaling of Distributed Events workers under load
• Maintainable — new business rules added via new classes, not if-else chains

Real-World Example 2 — CRM Lead Management

MANDATORY: Second complete example in a different domain — CRM Lead Management.

Business problem

Sales teams need real-time lead assignment, pipeline stages, and event notifications when leads change status or score.

Why Dependency Injection in ASP.NET Core solves it

In CRM Lead Management, Indian IT delivery teams (TCS, Infosys, Wipro lateral rounds) frequently ask how Dependency Injection in ASP.NET Core applies to distributed systems. This example shows production-level implementation with ASP.NET Core integration, not toy animal/car demos.

Production implementation

// REAL-WORLD EXAMPLE 2: CRM Lead Management
// ShopNest Enterprise Architecture — Distributed Events module
// Pattern: Dependency Injection in ASP.NET Core

namespace ShopNest.Architecture.DistributedEvents;

public interface IDependencyInjectioninASP.NETCoreService
{
    Task ExecuteAsync(DependencyInjectioninASP.NETCoreRequest request, CancellationToken ct = default);
}

public sealed class CRMLeadManagementDependencyInjectioninASP.NETCoreService : IDependencyInjectioninASP.NETCoreService
{
    private readonly ILogger _logger;

    public CRMLeadManagementDependencyInjectioninASP.NETCoreService(ILogger logger)
        => _logger = logger;

    public async Task ExecuteAsync(DependencyInjectioninASP.NETCoreRequest request, CancellationToken ct)
    {
        _logger.LogInformation("[Dependency Injection in ASP.NET Core] Processing {Domain} request {Id}",
            "CRM Lead Management", request.Id);

        // Production implementation — see Program.cs for DI registration
        await Task.Delay(10, ct);
        return Result.Success(request.Id);
    }
}

// Register in Program.cs:
// builder.Services.AddScoped();

Scalability benefits

• Supports multi-region deployment on Azure with independent scaling
• Integrates with ShopNest distributed events (RabbitMQ) for async workflows
• Redis caching reduces database load for read-heavy CRM operations
• Polly resilience policies handle transient failures in cloud-native environments

Pattern variations & ASP.NET Core integration

Modern C# 14 uses primary constructors, records, and DI. Register Dependency Injection abstractions in Program.cs with appropriate lifetimes — Singleton for stateless, Scoped for request-bound, Transient for lightweight factories.

Microservices: Apply Dependency Injection within bounded contexts — each ShopNest service (Distributed Events) owns its implementation.

Pattern comparison & when NOT to use

Compare Dependency Injection with similar patterns. Avoid overengineering — if a simple function or DI registration suffices, do not force a pattern. Senior architects value judgment over pattern count.

Unit testing the pattern

public class DependencyInjectionPatternTests
{
    [Fact]
    public async Task ExecuteAsync_ReturnsSuccess()
    {
        var mock = new Mock<IDependencyInjectionService>();
        mock.Setup(s => s.ExecuteAsync(default)).ReturnsAsync(Result.Success());
        var result = await mock.Object.ExecuteAsync(default);
        Assert.True(result.IsSuccess);
    }
}

Pattern recognition

Object creation pain → Creational. Composing subsystems → Structural. Algorithm/communication variation → Behavioral. Persistence/messaging → Enterprise. Multi-service → Cloud patterns. ASP.NET pipeline → Middleware/Options/Hosted Service.

Common errors & fixes

• Singleton with mutable state shared across requests — Use Singleton only for stateless services; keep request state Scoped.
• Factory explosion — new class per trivial variation — Use Strategy or simple DI when behavior differs slightly, not Abstract Factory.
• Repository wrapping every EF call without domain logic — Repository adds value for testability and query composition — not as a pass-through.
• Saga/CQRS on a CRUD app with 3 tables — Start with simple layered architecture; add patterns when complexity demands.

Best practices

• 🟢 Name patterns by problem solved, not GoF catalog page number
• 🟢 Register abstractions in DI — depend on interfaces, not concretions
• 🟡 Match DI lifetime to pattern (Singleton vs Scoped)
• 🟡 Write one xUnit test proving the pattern's core behavior
• 🔴 Do not apply Saga/CQRS/Event Sourcing on simple CRUD
• 🔴 Document when you chose NOT to use a pattern — interviews love this

Interview questions

Fresher level

Q1: What is the Dependency Injection pattern and when would you use it?
A: Dependency Injection solves a specific recurring problem on ShopNest Distributed Events. Explain intent, structure (participants), and one real example — then state when NOT to use it.

Q2: Dependency Injection vs similar patterns — how do you choose?
A: Compare intent and consequences; e.g. Strategy vs State, Repository vs DAO, Mediator vs Observer — pick by change axis.

Q3: How do design patterns relate to SOLID?
A: Patterns implement SOLID — Strategy/OCP, Repository/DIP, SRP via focused classes. SOLID is why; patterns are how.

Mid / senior level

Q4: Repository pattern — benefits and pitfalls?
A: Benefits: testability, query composition. Pitfalls: leaky abstraction, generic repo anti-pattern, duplicating EF features.

Q5: When would you NOT use a design pattern?
A: Simple CRUD, prototypes, or single-developer utilities — YAGNI until complexity appears.

Q6: How are patterns asked in TCS/Infosys lateral interviews?
A: Scenario-based: "Design payment retry" → Retry + Circuit Breaker; "Split monolith" → Strangler + API Gateway.

Coding round

Implement Dependency Injection for ShopNest Distributed Events: interface, concrete class, DI registration, and xUnit test with Moq.

builder.Services.AddScoped<IDependencyInjectionService, DependencyInjectionService>();

public sealed class DependencyInjectionService : IDependencyInjectionService
{
    public Task<Result> ExecuteAsync(CancellationToken ct) => Task.FromResult(Result.Success());
}

Summary & next steps

• Article 60: Dependency Injection in ASP.NET Core — Complete Guide
• Module: Module 7: ASP.NET Core Architecture Patterns · Level: ADVANCED · Type: ASPNET
• Applied to ShopNest Enterprise Architecture — Distributed Events

Previous: Pipeline Pattern in ASP.NET Core — Complete Guide
Next: Minimal API Pattern — Complete Guide

Practice: Apply today's pattern in one module — commit with feat(patterns): article-60.

FAQ