dependency-injection-autofac

Wiring Autofac modules for dependency injection involves creating one Autofac Module per layer (Domain, Application, Infrastructure) to organize registrations. This module-per-layer pattern ensures centralized registrations and correct lifetimes for scalable, testable application wiring.

Register MediatR handlers and FluentValidation validators with Autofac using assembly scanning within the Application layer's module. This approach automatically discovers and wires handlers and validators, simplifying configuration and maintaining clean architecture boundaries.

The recommended Autofac lifetime scope for DbContext and repositories ensures scoped or per-request lifetimes, preventing concurrency issues. Applying defined lifetimes per component guarantees that EF Core DbContext and repository implementations maintain scalable and testable application wiring.

Yes, this Autofac dependency injection approach works specifically for service-oriented projects using Domain, Application, and Infrastructure layers. It covers module loading, registration in the API host, and defined component lifetimes to support clean architecture.

Integrate Autofac as the DI container in your .NET API host Program.cs by wiring Autofac modules into the host configuration. You create a main module that registers DomainModule, ApplicationModule, and InfrastructureModule to centralize application wiring.

Using a module-per-layer pattern for dependency injection organizes registrations cleanly across Domain, Application, and Infrastructure layers. This separation ensures scalable, testable, and maintainable application wiring compared to monolithic centralized registration approaches.