This website uses cookies

Our website, platform and/or any sub domains use cookies to understand how you use our services, and to improve both your experience and our marketing relevance.

This holiday season, maximize your sales through enhanced website performance and 24/7 caring support. SAVE 30% NOW

Dependency Injection In Magento 2

Updated on  5th September

3 Min Read
Dependency Injection Magento 2
Reading Time: 3 minutes

In programming languages, a dependency is known as the object which is needed by a class to perform some functions. Injection is the passing of that particular dependency to a dependent object/class. The real meaning of Dependency Injection is to inject the dependency into the class from another source. In this post, we’ll discuss Magento 2 Dependency Injection.

For example, if you have defined a Class in Magento 2 that fetches some data by using Magento 2 Helper Class, we can say that your Class has a dependency of that Magento 2 Helper Object.

Still confused? Let’s take a simple scenario. You are constructing a house, and you begin with the pillars and walls. At the entry point, when you think to get the main gate, what will do you? Would you start building a custom gate out of the wood, iron or other raw materials? Or would you take it directly from a vendor and install it, hassle free?

That’s absolutely right! The most pragmatic approach is to buy the ready-made gate from a vendor and to simply install it. And that is what Dependency Injection does. It decouples your class from the construction of its dependency.

There is nothing wrong with the above code. It will return the first & last name without any issues. But the Customer class is tightly coupled with the CustomerInfo class. If you add a new parameter to the constructor of Customer class, then you have to modify every class where you had created a Customer object with the new operator, which subjects it to a tedious and lengthy process, especially when it comes to the large applications.

Dependency Injection solves these issues by injecting the dependencies through the dependent class’ constructor. The result is highly maintainable code which can be used in long-term projects. It might look like this:

In the above code, instead of instantiating dependency with the new operator, we defined it in a __construct parameter. It is known as Automatic Dependency Injection. Yes! The previous example might be easy for you, but believe me, we don’t need them in latest programming techniques.

By using Automatic Dependency Injection (ADI), the object doesn’t need to look for another dependent object. There are three types of Automatic Dependency Injections:

  • Constructor Injection: The most common way to inject dependencies is via a class’s constructor. To do this, you need to add an argument to the constructor signature to accept the dependency.
  • Setter Injection: Another possible method to inject a dependency into a class is by adding a setter function that takes the dependency.
  • Interface Injection: The interface injection defines and uses interfaces for the dependency injection.

Magento 2 uses Automatic Dependency Injection (ADI) which is further derived to the Constructor Injection. It means in Magento 2, passing the objects in the constructor’s parameters will help you follow the injection rules. Dependency Injection in Magento 2 is an alternative to the Mage Class method of Magento 1. Below example will give you an idea that how it will look like in Magento 2.

Helper Class in Magento 2 (Data.php):

Calling HelperFunc() using DI:

In above code class, you can see how Dependency is injected into the constructor of the class. You can use this method anywhere in Magento 2.

The Object Manager can also do this magic. We can call the create() method of ObjectManager, to create the object for your class, gets and passes the value for the constructor parameter from instance configuration (di.xml) files. But you should never use ObjectManager!!

ObjectManager defeats the purpose of Dependency Injection. The advantage of using ObjectManager is less code to write, but it doesn’t follow the Magento 2 Development Processes and also creates the hidden dependencies which are not required.

It is still used somewhere in the core of Magento 2, but it will get refactored soon. So, the best recommendation is, DO NOT USE THE OBJECTMANAGER. It is a good practice to know what the code depends on, rather than having hidden dependencies in the middle of the code. That is why Magento 2 Dependency Injection is preferred by the structure.


It is necessary to follow the code patterns while doing development on Magento 2. Magento Community recommends using Magento 2 Dependency Injection rather than ObjectManager. It was a short introduction of DI, Automatic DI, Constructor Injection and Object Manager in Magento 2.

There is a lot more to learn about each topic very deeply. Stay in touch for more. 🙂 Have any questions? Write in the comments section and I will get back to you!

Share your opinion in the comment section. COMMENT NOW

Fayyaz Khattak

Fayyaz is a Magento Community Manager at Cloudways - A Managed Magento Hosting Platform. His objective is to learn & share about PHP & Magento Development in Community. Fayyaz is a food lover and enjoys driving. You can email him at

Start Growing with Cloudways Today.

Our Clients Love us because we never compromise on these

Get Our Newsletter
Be the first to get the latest updates and tutorials.