The Adobe Commerce Architect Master (AD0-E722)

To add a product type with custom pricing, the Architect needs to do the following steps:

Create a content of the etc/product_types.xml file that defines the new product type, its label, model, index priority, and price model.  This file is used to register the new product type and its associated classes in Magento 1 .

Create a new price model that extends \Magento\Catalog\Model\Product\Type\Price and implements the custom pricing logic for the new product type.  The price model is responsible for calculating the final price of the product based on various factors, such as special price, tier price, catalog price rules, etc 2 .

Create a custom type model that extends from the abstract Product Type model (\Magento\Catalog\Model\Product\Type\AbstractType) and overrides the methods related to the product type behavior, such as prepareForCart, getAssociatedProducts, etc.  The type model defines how the product type interacts with other components, such as quote, order, cart, etc 3 .  References :

How to add a new product type in Magento 2? (MageStackDay mystery question 1) - Magento Stack Exchange

Magento 2: How to create custom product types - BelVG Blog

Magento 2: How to create custom product types - BelVG Blog

To make sure the vcl_hash function of Varnish considers the newly created attribute, the Architect needs to do the following steps:

Create a new class that implements the Magento\GraphQlCache\Model\CacheId\CacheIdFactorProviderInterface interface. This interface defines two methods: getFactorName and getFactorValue. The getFactorName method should return the name of the attribute, in this case, my_attribute.  The getFactorValue method should return the value of the attribute for the current customer, which can be obtained from the customer session or customer repository 1 .

Add this class to the idFactorProviders array of Magento\GraphQlCache\Model\CacheId\CacheIdCalculator through dependency injection. The CacheIdCalculator is responsible for generating a cache ID for each GraphQL request based on the factors provided by the idFactorProviders.  By adding the new class to this array, the Architect ensures that the cache ID will include the value of my_attribute 1 .

The cache ID is then used by Varnish to hash and lookup the cached response for each request.  By including my_attribute in the cache ID, the Architect ensures that Varnish will serve different responses based on the attribute value of the customer 2 .  References :

Magento_GraphQlCache module | Magento 2 Developer Documentation

Varnish caching | Adobe Commerce 2.4 User Guide - Magento

The carrier model class can implement caching methods to store and retrieve the quotes from the API based on the request parameters. This can reduce the number of API calls and improve the performance of the shipping rate calculation. The _setCachedQuotes() method can save the response from the API to a cache storage, and the _getCachedQuotes() method can check if there is a cached response for the current request and return it if it exists.  References :  Caching in carrier model ,  Carrier model interface

The product price index can be optimized by using parallel mode and customer group merging. Parallel mode allows the indexer to run multiple threads simultaneously, which can speed up the indexing process. Customer group merging reduces the number of rows in the price index table by merging customer groups that have the same product prices. This can improve the performance of the price index queries and reduce the index size.  References :  Indexing optimization ,  Price index customer group merging

Using an iframe system for payment integration can help reduce the PCI scope and compliance burden for the merchant, as the payment data is collected and processed by the payment service provider (PSP) within the iframe, without touching the merchant’s website or server. This way, the merchant can leverage the PSP’s PCI certification and avoid storing or transmitting any sensitive cardholder data on their own system. The iframe also provides a secure barrier between the host webpage and the loaded page, preventing any access or manipulation of the payment data by malicious actors.  To implement this approach, the merchant needs to embed the PSP’s payment form in their checkout page using an iframe element, and configure the communication between the iframe and the host page using JavaScript 1 2 3 .

The issue is being caused by the high coupling between objects (CBO) value of the class MyService.  CBO is a metric that measures the number of classes that are coupled to a given class, either by method calls, property or parameter references, inheritance, or constants 1 .  A high CBO value indicates that the class is too tightly coupled with other classes, which makes it more difficult to maintain, test, and reuse 2 . To reduce the CBO value, the Architect should introduce a new class that encapsulates the five scalar parameters that configure the behavior of MyService. This way, the constructor of MyService will only have one parameter of the new class type, instead of five scalar parameters. This will also make the code more readable and maintainable, as the new class can provide methods to access and manipulate the configuration data.  The constants referencing other classes should not be consolidated into a string representation, as this would not reduce the CBO value and would make the code less clear and type-safe 3 .  The number of different classes and interfaces referenced anywhere inside the class is not relevant for the CBO metric, as it only counts the classes that are coupled to the given class 1 .  References :  CBO coupling between object ,  Coupling Between Object classes (CBO) ,  Cohesion and coupling of an object in OO programming

This action is necessary to make the attribute available for content staging and preview. According to the Adobe Commerce documentation, the catalogstaging_category_update_form.xml file defines the fields that are displayed in the Scheduled Changes section of the category form. The file extends the category_form.xml file and adds additional fields that are specific to content staging, such as start and end dates, campaign name, description, etc. To include a custom category attribute in the Scheduled Changes section, the attribute must also be declared in the catalogstaging_category_update_form.xml file with the same configuration as in the category_form.xml file.

References :

Content staging | Adobe Commerce Developer Guide

Create a category attribute | Adobe Commerce Developer Guide

Developer mode is the best option for setting up a development environment for testing functionality, not performance, before being passed to the testing team. In developer mode:

Errors are logged and hidden from the user. This ensures that the user does not see any uncaught exceptions or debugging information, but the developers can still access them from the log files.

Cache mode can only be changed from command line. This prevents any accidental or unauthorized changes to the cache settings from the admin panel or other sources.

Static files are created dynamically and then cached. This allows the developers to see the latest changes to the static files without having to run the static content deployment command every time. The static files are also cached for faster loading.

References : https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/setup/application-modes.html?lang=en#application-modes 1