Dependency Injection Of Software Design Principle

Dependency Injection Of Software Design Principle

Dependency Injection is design pattern in which one object supplies the dependencies of another object rather than calling itself. This design pattern follows “Dependency Inversion” of software design principle.
This Principle state that-
High Level modules should not depend on Low Level modules. Both should depend on abstractions.
Abstractions should not depend on details. Details should depend on abstraction.

First of all understand what is High level module and Low level module?
High level module means similar to classes which encapsulates complex operations and Low level module means it implements basic and primary operations. This both modules should not depend on each other but both should be depend on abstraction which remove dependency.
Let\'s understand by real-world example:-

Fan is object which performs various operations when it gets current or power after switch button is press. Here who is High level module Fan and Low level module is Switch Button. As per situation both module depend on each other but the main service is communicate between them is current or power and both module in this example depend on current or power service which act as an interface.
So from this example prove that “High Level modules should not depend on Low Level modules. Both should depend on abstractions”.

The main aim of this principle is to implement any (web, distributed , Dashboard, windows) application in loosely coupled pattern which given benefits like if we want do any changes in low level module which not affected on high level module.

To implement Dependency Inversion principle in application implement one technique which is “Dependency Injection” which achieving or inject dependency to a class by using three ways-
• CONSTRUCTOR

• METHOD

• SETTER PROPERTY

====================================================================
This blog by Visual Coder (Division of SQUAD Infotech Pvt. Ltd.)
About