Going bananas with loose coupling and dependency injection

Question

With the latest additions to our dependency injection framework (annotations in spring), the marginal cost of creating DI-managed components seems to have hit some critical new

Answer 1

Pure DI perfect universe, I think single classes+method design is ideal. In reality we need to balance the cost of that which makes it less feasible.

Cost factors

• Overhead of DI. Spinning up all the underlying and related underlyings for a single method is expensive. Grouping into a class allows us to offset some of that.
• Skills - DI is new to many (myself ESPECIALLY) so understanding how to do it better or get out of old/habitual designs is tough
• Brown field apps which have them already, it's easier/cheaper/quicker to live with them and worry about this in future green field apps

Hopefully my newbie-ness (yes, I am filled with made up words) with DI hasn't made me completely wrong with this.