I use dependency injection pattern on all projects where it makes any sense, especially spring is following me all my life. Once I've discovered domain driven design , I've realized that model should be rich, clear, reusable, no meaningless dependencies. Combining of clear model along with spring annotation can bring few issues except model dependency on spring jar files. See following example what's going on: And relevant unit tests. Once you decided to write reboust component, you can't be absolutely sure that someone will use spring (or other DI framework) to push all dependencies. Well, you need them check. Those are the reasons why I decided to use dependency injection via constructor. The componets just use fully supplied constructor requiring all mandatory dependencies. See the code: Advantages Such code brings couple of other advantages which you must not see at a glance: Obviously clearer code as there is just only one place where all