How do you design an application to prevent the DI container from becoming a God Dependency?

Applications should follow the Hollywood Principle: 'Don't call us, we'll call you.' Business logic should never reference the DI container directly.

If your domain objects reference IServiceProvider or Container, your domain is tightly coupled to infrastructure. Instead, push all DI logic to the absolute outermost layer (Composition Root, APIs, Background Workers). The inner layers should only consist of plain classes (POCOs/POJOs) with explicit constructor dependencies.