DIP vs. DI vs. IoC [closed]

Answer 1

My 20c, start coding. You probably have at least a rough idea of how it works. Coding a proof of concept (POC) is going to be a great way to see how things fit together and work at dev and run time. Reading will only take you so far, doing will really help make it click.

If you don't know where to start, most blog posts about DI have simple examples that you can run up. Don't get stuck on which framework to use (Unity, Spring, Castle Windsor etc) because it really doesn't matter for a POC.

Answer 2

My take on it is this: DIP is the principle that guides us towards DI. Basically, loose coupling is the goal, and there are at least two ways to achieve it.

• Dependency Injection
• Service Locator

However, Service Locator is an anti-pattern and has nothing to do with the DIP. DI, however, is the correct application of the DIP.

The relationship between DI and IoC has been explained before.

BTW, when talking about DI and loose coupling, I find the terminology laid out in Domain-Driven Design the most applicable. Basically, Services are the only kinds of objects subjected to DI.