Dependency Injection (DI)

Mastering Dependency Injection: The 20-Year Architect's Manifesto

In my 20 years of building global enterprise systems, I've seen DI evolve from a "nice-to-have" pattern to the absolute backbone of the .NET ecosystem. If you don't master DI, you aren't building a system—you're building a house of cards.

1. WHAT is Dependency Injection? (The Deep Dive)

Dependency Injection (DI) is a software design pattern that implements **Inversion of Control (IoC)**. In simple terms: a class should NEVER create its own dependencies (like a database service or an email service). Instead, an external "Container" provides these objects to the class.

2. WHY do we use DI? (The Senior Architectural Reasons)

Loose Coupling: If your PaymentService is hardcoded to use Stripe, switching to PayPal requires a full rewrite. With DI, you switch a single line in Program.cs.
Unit Testability: You cannot test a "Hardcoded" class. With DI, you "Inject" a Mock/Fake service during testing, allowing you to test logic without actually charging a credit card or sending an email.
Object Lifecycle Management: DI handles the Creation and Disposal of objects, preventing memory leaks that crash production servers.

3. The 3 Pillars of Service Lifetimes (Critical Mastery)

1. Transient

Created **EVERY TIME** they are requested. Use this for lightweight, stateless services (e.g., a simple Calculator or Formatter).

2. Scoped

Created **ONCE PER HTTP REQUEST**. This is the standard for DbContext and Unit of Work. All components in a single web request share the same instance.

3. Singleton

Created **ONCE AND SHARED GLOBALLY** for the entire life of the app. Use this for Caching engines, Configuration, or State machines.

4. THE "4 WAYS" TO INJECT (Mastery Level)

A junior only knows Constructor Injection. An L6 Architect knows all four:

Constructor Injection (Standard): Most common. The dependency is required for the class to exist.
Action Method Injection ([FromServices]): Use this when only **ONE Action Method** in your controller needs a service (Save memory and CPU cycles!).
View Injection (@inject): Inject services directly into your .cshtml files (e.g., a Global Settings service or a Navbar provider).
Property Injection (Non-Native): Rarely used in native .NET, but supported by third-party containers like Autofac for optional dependencies.

5. REAL-TIME ENTERPRISE EXAMPLES

Example 1: Multi-Provider Payment Gateway (Keyed Services - .NET 8)


// The Register (.NET 8 Keyed Services)
builder.Services.AddKeyedScoped<IPaymentService, StripeService>("Stripe");
builder.Services.AddKeyedScoped<IPaymentService, PayPalService>("PayPal");

// The Controller
public class CheckoutController : Controller {
    public IActionResult Pay([FromKeyedServices("Stripe")] IPaymentService stripe) {
        stripe.Process(100.00m);
        return View();
    }
}

6. BENEFITS, PROS & CONS (The Technical Audit)

BENEFITS & PROS

**Clean Architecture:** Keeps Business Logic separate from Infrastructure.
**Maintainability:** Changes in implementation don't break the UI.
**Parallel Development:** Teams can work on Interfaces without the full logic.

CONS & RISKS

**Initial Complexity:** Steeper learning curve for "Page-Based" developers.
**Performance Overhead:** Minor overhead during object resolution in the DI container.
**Runtime Errors:** If you forget to register a service, the app crashes only when the page is called.

THE ARCHITECT'S NIGHTMARE: Captive Dependencies

The most dangerous pitfall: Injecting a Scoped service into a Singleton. The Singleton (which never dies) will "Capture" the Scoped service (which should die after the request). This will cause **Database Deadlocks**, Thread Starvation, and Data Corruption across different users! In a 20-year career, I've seen this destroy multi-billion dollar deployments in minutes. Always audit your service lifetimes.

7. INTERVIEW MASTERY: 20-Year Senior Answer

Question: "How do you handle multiple implementations of the same interface?"

Architect Answer: "In modern .NET 8, I use Keyed Services for clean, declarative selection. In older versions, I would inject an IEnumerable<IService> and use a Factory Pattern or LINQ to select the correct implementation based on a string discriminator. This ensures we stay within the **SOLID Principles (O - Open/Closed)**, allowing us to add new providers without modifying existing code."

Interview Q&A for this course