{"id":64036,"date":"2016-11-12T18:12:04","date_gmt":"2016-11-12T18:12:04","guid":{"rendered":"http:\/\/webkul.com\/blog\/?p=64036"},"modified":"2025-12-31T14:00:23","modified_gmt":"2025-12-31T14:00:23","slug":"magento2-proxy-design-pattern-code-generation","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/magento2-proxy-design-pattern-code-generation\/","title":{"rendered":"Magento2 Proxy Design Pattern And Code Generation"},"content":{"rendered":"\n

Magento 2 uses the Proxy design pattern<\/strong> to improve system performance. It helps manage heavy objects that consume high memory. The system creates a “placeholder” instead of the real object. This ensures that Magento only initializes expensive classes when they are actually needed.<\/p>\n\n\n\n

What is a Proxy?<\/h2>\n\n\n\n

A Proxy is a class that replaces another class. It shares the same interface as the original object. Magento generates these classes automatically during the code compilation process. By using proxies, you prevent unnecessary object instantiation during the bootstrap phase.<\/p>\n\n\n\n

Why Use Proxies in Magento 2?<\/h2>\n\n\n\n

Most Magento 2 classes use Constructor Injection<\/strong>. If a class has ten dependencies, Magento loads all ten immediately. Some dependencies might be “heavy” or rarely used. A Proxy stops this “chain reaction” of loading, which speeds up your application significantly.<\/p>\n\n\n\n

What is the proxy design pattern ?<\/h2>\n\n\n\n

The Magento 2 Proxy Design Pattern<\/strong> is a structural design pattern. It works as a placeholder for another object. The real object is created only when it is actually required. This approach is known as lazy loading. Magento uses proxies to avoid heavy object initialization during class construction.<\/p>\n\n\n\n

Lets understand why this problem comes in magento2.<\/p>\n\n\n\n

Problem:<\/strong><\/p>\n\n\n\n

Magento 2 supports multiple types of dependency injection, with constructor injection and method injection used most frequently.<\/p>\n\n\n\n

Constructor injection introduces a performance issue. When a class is instantiated, Magento immediately creates all objects injected into its constructor.<\/p>\n\n\n\n

This behavior triggers a chain reaction where Magento creates multiple dependent objects at once. As the number of dependencies increases, the instantiation process becomes slower and resource-intensive.<\/p>\n\n\n\n

To prevent this chain reaction and improve performance, Magento uses the Proxy Design Pattern, which enables lazy loading of dependencies.<\/p>\n\n\n\n

Solution:<\/strong><\/p>\n\n\n\n

Magento solves this performance problem by using the Proxy Design Pattern.<\/p>\n\n\n\n

Instead of creating all dependencies during class instantiation, Magento injects a proxy class into the constructor. The proxy acts as a placeholder for the actual dependency. Magento creates the real object only when the code actually uses it.<\/p>\n\n\n\n

This approach delays object creation and avoids unnecessary instantiation. As a result, Magento reduces memory usage and improves overall performance.<\/p>\n\n\n\n

The Proxy Design Pattern enables lazy loading while keeping constructor injection clean and maintainable.
Example:<\/p>\n\n\n\n

 <type name="Magento\\Catalog\\Model\\Product">\n    <arguments>\n        <argument name="catalogProductStatus" xsi:type="object">\n             Magento\\Catalog\\Model\\Product\\Attribute\\Source\\Status\\Proxy\n        <\/argument>\n\n        <argument name="productLink" xsi:type="object">\n             Magento\\Catalog\\Model\\Product\\Link\\Proxy\n        <\/argument>\n    <\/arguments>\n<\/type><\/pre>\n\n\n\n
The above entry comes from the Catalog module\u2019s di.xml<\/code><\/strong> file.
In the type<\/code> declaration for the Magento\\Catalog\\Model\\Product<\/code> class, Magento replaces the constructor arguments catalogProductStatus<\/code> and productLink<\/code> with their corresponding Proxy classes<\/strong>:<\/p>\n\n\n\n