What is the business case for a dependency injection (DI) framework?
Posted
by kalkie
on Stack Overflow
See other posts from Stack Overflow
or by kalkie
Published on 2010-05-16T10:44:39Z
Indexed on
2010/05/16
10:50 UTC
Read the original article
Hit count: 139
Filed under:
dependency-injection
|business
|architecture
|object-oriented-design
|inversion-of-control
At my company we want to start using a dependency injection (DI) framework for managing our dependencies. I have some difficulty with explaining the business value of such a framework. Currently I have come up with these reasons.
- Less source code, delete all the builder patterns in the code.
- Increase in flexibility. Easier to switch dependencies.
- Better separation of concern. The framework is responsible for creating instances instead of our code.
Has anybody else had to persuade management? How did you do that? What reasons did you use?
© Stack Overflow or respective owner
