golang-dependency-injection

Dependency injection in Go is best implemented using explicit constructor injection, passing dependencies through interfaces at the composition root to enable easy mocking and testing. This approach keeps wiring explicit and avoids global state.

The service locator anti-pattern occurs when a DI container is passed around and used to resolve dependencies dynamically at runtime. This Skill guides keeping the container at the composition root and injecting dependencies via interfaces to avoid tight coupling.

Choosing between Wire, dig/fx, and samber/do depends on project size and lifecycle needs. This Skill provides library comparisons, guiding when to use manual wiring versus DI libraries for small services or large microservices.

Yes, the dependency injection guidelines and library comparisons provided are compatible with Go 1.18 and later versions. The patterns apply to architectures ranging from small services to large microservices.

You should avoid init-based setup when it creates hidden dependencies and global state that hinder testing. This Skill recommends explicit constructor injection at startup to ensure maintainability and clean wiring.