dotnet:di-patterns

The correct dependency injection lifetime for DbContext in .NET is Scoped. Following this lifetime management practice ensures proper context handling within a request scope, preventing concurrency issues and maintaining code maintainability.

You manage HttpClient dependencies by leveraging IHttpClientFactory to avoid socket exhaustion. This .NET dependency injection pattern ensures proper lifetime management and prevents DNS changes issues, improving application performance.

A captive dependency in .NET dependency injection occurs when a Singleton service captures a Scoped instance. This anti-pattern forces the Scoped dependency to live as long as the Singleton, breaking lifetime management and causing concurrency bugs.

Using IServiceProvider as a service locator is an anti-pattern because it hides class dependencies, making code maintainability harder and testing difficult. Explicit dependency injection patterns are preferred for clear dependency resolution.

Use Transient dependency lifetimes for lightweight, stateless services and Singleton for shared state or expensive initialization in .NET. Reviewing lifetime management best practices ensures optimal performance and code maintainability.