ContextQMD
Back to Cleanarchitecture

ADR 001: Replace Autofac with .NET Core Dependency Injection

docs/architecture-decisions/adr-001-dotnet-di-adoption.md

11.1.12.1 KB
Original Source

ADR 001: Replace Autofac with .NET Core Dependency Injection

Status

Accepted

Context

Initially, this repository employed Autofac for dependency injection. At the time of adoption, Autofac was preferred due to its robust feature set, including:

  • Support for advanced scenarios such as decorators and modules, which could be placed close to their corresponding implementations.
  • A well-established history of stability and maturity, having been used in various projects before .NET Core's built-in DI was fully featured.

As the .NET ecosystem evolved, the built-in DI container began to meet the needs of our project without introducing the added complexity associated with Autofac. The .NET DI framework has matured significantly, offering sufficient functionality for typical use cases, including:

  • Improved support for configuration through extension methods.
  • A simpler learning curve for new contributors familiar with .NET conventions.

Decision

Based on community feedback and a review of our project's requirements, we have decided to remove Autofac from this template and transition to using .NET's built-in dependency injection infrastructure. This decision aligns with the goal of simplifying the codebase and reducing external dependencies.

Consequences

  • Simplified Codebase: Removing Autofac results in a cleaner, more maintainable codebase that adheres to .NET standards.
  • Reduced Complexity: The transition eliminates the need for additional files and configurations specific to Autofac, making the project easier to understand for new contributors.
  • Standardization: Adopting .NET's built-in DI promotes consistency with other .NET projects, making it easier for developers familiar with the framework to contribute effectively.

References