Dependency Inversion Control
Dependency Inversion Principle (DIP) is one of the five software design principles. What programming languages you know, you should know these five principles written below :
Open Close Principle(OCP)
Dependency Inversion Principle (DIP)
Interface Segregation Principle (ISP)
Single Responsibility Principle (SRP)
Liskovās Substitution Principle (LSP)
In this article, i will explain Dependency Inversion Principle.
Purpose / Reason
This principleās purpose is not to provide strong correlation between high level classes and low level classes. The reason of using DIP is that changing in low level class shouldnāt affect high level class. When you need some change in low level classes, you shouldnāt need to change code in high level classes. For clarifying , letās see a bad example and good example respectively, thus, you can understand better.
Key Principles
High level classes should not depend on low level classes. Both should depend on abstractions.
Abstractions should not depend on details. Details should depend on abstractions.
Implementation
For this case, you build log manager 6 months ago to track userās action. For this aim, you decided to insert log into database. But right now, your manager wanted that log must be inserted into file.
Bad Example :
Here is the code that you wrote 6 months ago to track user actions.
public class LogDB { public void AddLog() { // Add log into database } } public class LogManager { LogDB log = new LogDB(); public LogManager(LogDB log) { this.log = log; } public void Log() { this.log.AddLog(); } }
Here is the new low level class you write to insert log into file. It needs to be implemented current structure.
public class LogFile { public void AddLog() { // add log into file } }
When you try to implement LogFile into current class structure. You will have to change LogManager classes. Using this bad solution, you have these problems written below :
The code statement where you used to invoke LogManager.Log() method.
You have to redone your unit testing.
Itās obvious, you are able to implementing new requirements into your current code. However, it wonāt be a good solution. Because, you will need to modify all related classes to Log Business Logic.
Letās see how you can build better using Dependency Inversion Principle
Good Example :
According to this principle, the way of building class structure is to start from high level classes to Ā low level classes. And put abstract class or interface between high level classes and low level classes.
High Level Classes ==> Abstraction ==> Low Level Classes
//ILog is a abstraction. public interface ILog { void AddLog(); } // LogManager is a high level class public class LogManager { ILog log; public LogManager(ILog log) { this.log = log; } public void Insert() { this.log.AddLog(); } } // LogDB is a low level class public class LogDB : ILog { public void AddLog() { // insert log into database } } // LogFile is a low level class public class LogFile : ILog { public void AddLog() { //insert log into file } }
If you build your class structure in respect of DIP, you can implement new low level class such as LogFile without changing any code in your high level class ( LogManager ). Also you minimize the risk to affect old functionality. Beside that, you donāt need to rewrite your unit testing for LogManager class.
For this good example, as you see, LogManager (High Level Class) doesnāt know anything about low level classes. It knows only interface of log classes (ILog).
When you use DIP, you have more flexible. But this principle can not be applied for every class. If you have a class functionalities these are more likely to remain same, unchanged in the future, you donāt have to apply this principle.
