Contents
What kind of design pattern does Magento use?
Magento utilizes a unique MVC pattern, utilizing a DOM based configuration layer. It leverages xml to drive the configuration and actions of the application on top of the regular Model-View-Controller architecture. Magento uses the Front Controller pattern to implement workflows for it’s application.
What’s the difference between Magento and Magento 2?
Magento 2 is an extension based or modular system, which allows a third-party developer to customize and overwrite core parts of its framework. These customization may lead to several issues, for example, it will become difficult for developers to keep track of customization done by external extensions.
Why do we need factory classes in Magento 2?
In Magento 2 Factory classes create a layer between the object manager and business code. Factory classes does not needs to be defined explicitly as they are auto-generated. We should create factory classes for non-injectable objects.
What is the role of Object Manager in Magento?
Object manager has a very big role to play, Magento prohibits the direct use of it. Object manager is responsible for implementing factory, singleton and proxy patterns. It automatically instantiates parameter in class constructors. They does not have their own identity such as EventManager, CustomerAccountManagementService.
When did the Gang of Four define design patterns?
In 1994, they published a book (Design Patterns: Elements of Reusable Object-Oriented Software) for explaining the concept of Design Patterns. The 23 Design patterns are defined by the Gang of Four programmers. These 23 patterns are divided into three groups depending on the nature of the design problem they intend to solve.
Are there any cross cutting concerns in Magento 2?
There are various cross-cutting concerns in Magento 2 which have to go through all modules. Few examples of cross-cutting concerns are security, monitoring, and logging. In the “Key Insights into Development Design Patterns in Magento 2” presentation the following Design Patterns covered:
How is an object manager used in Magento?
Large applications, such as the Magento application, use an object manager to avoid boilerplate code when composing objects during instantiation. In the Magento framework, the implementation of the ObjectManagerInterface performs the duties of an object manager. Object creation in factories and proxies.