On the last Monday morning, when I was reading " this blog " I came across this term 'injector' for enough time to give it a thought and dig into it. and That's how I got started with it. DI: stands for Dependency Injection (ugh! what a fancy and confusing name!) It is a very famous code pattern to make the codebase more cohesive and loosely coupled. Often, while coding, we write some classes which internally initialize the objects of other classes. And thus the earlier class become dependent on the object creation of the later class. But, thoughtfully speaking, a class should be cohesive and should do nothing more than it's a purpose. For example, we have a class Employee and a class Address . Where an object of class Address is aggregated inside Employee class. Thus, Employee class, while providing a blueprint of an Employee object, now manages the creation of Address object too. This adds up the dependency and makes the class, less cohesive.
I write, so that I may learn.