Indeed. But sometimes you need "magic". If you have a developer that is working on a specific part of an application, building business logic that does not req

Indeed. But sometimes you need "magic". If you have a developer that is working on a specific part of an application, building business logic that does not require her to know how MQ transactions are handled, or which database drivers are used, using a DI framework like Spring or Guice may help. These frameworks may add some overhead, but they also make unit testing, documentation and reduce code complexity of business logic. I guess it depends on the team you are working with. If you have solid, experienced engineers who understand the business domain, using Spring may not be relevant. But if you have a team that have different levels of skills and experience, a framework that abstracts away some of the underlying complexity is useful. If you are building a real time trading system, you probably don't want to use Spring because you want to control each and every component. But for most other projects it can be useful. Btw - your link mentions TDD. What tools did you use? (just out of curiousity..)