concept Constructor Over - injection in category dependency injection

appears as: Constructor Over-injection
Dependency Injection

This is an excerpt from Manning's book Dependency Injection.

Prevent the use of Property Injection as a solution to Constructor Over-injection. Classes with many Dependencies are a code smell and Property Injection won’t lower the class’s complexity. We’ll discuss Constructor Over-injection in section 6.1.

We’ve found the use of domain events to be an effective model. It allows code to be defined on a more conceptual level, while letting you build more-robust software, especially where you have to communicate with external systems that aren’t part of your database transaction. But no matter which refactoring approach you choose, be it Decorators, Facade Services, domain events, or perhaps another, the important takeaway here is that Constructor Over-injection is a clear sign that code smells. Don’t ignore such a sign, but act accordingly.

Because Constructor Over-injection is a commonly recurring code smell, the next section discusses a more subtle problem that, at first sight, might look like a good solution to a set of recurring problems. But is it?