Magento 2 and Adobe Commerce web applications are built using a combination of in-house custom code and third-party libraries. The first-party(in-house) code leverages functionality from typically open-source Also Magento has 3-d party libraries installed via composer. These modules will typically be deployed to the webserver serving the web application along with the in-house code.

The packages are most commonly downloaded from public registries such as Packagist taking advantage of the open-source ecosystem. It is also common for organizations to utilize private registries to mirror the public index or distribute internal packages which cannot be published publicly. The most famous is…

As a continuation of the Magento Performance tests epic, we will test the performance of the Magento Cloud (Adobe Commerce Cloud) Lafayette 148 New York website. I have found this Sucess Story on the Adobe official website:

Adobe Lafayette 148 Sucess Story

In the wake of the pandemic, Lafayette 148 needed to put some long-term plans into action — and develop additional revenue streams. In June of 2020 they quickly announced plans to launch a new division of the business called AtelierDirect. …

Let’s test the Oracle Cloud ARM Ampere server performance with Magento 2 and compare it with the Adobe Magento Commerce Cloud solution.

We will use a new Oracle Cloud ARM instance offering.

To create a Magento instance we need :

Step 1: Select OS.

Magento Grids are used to represent, filter, and sort various data in the Magento backend. They are also used to perform mass actions such as updates and deletes. This tutorial will show you how to create a simple admin grid.

Let's check how Magento an Adob Commerce Implemntation UI architecture implementation is different from the React JS grid.

Magento 2 exploits Knockout JS files in the frontend. It executes a Model View View-Model design outline which is very handy to create a dynamic UI.

To create a Magento grid, you need the next step :

the following steps you should…

Magento 2 uses Dependency Injection to replace functionality provided by the Mage class in Magento 1.x.

Dependency Injection is a design pattern that allows object A to declare its dependencies to an external object B that supplies those dependencies. The dependencies declared by A are usually class interfaces, and the dependencies B provides are concrete implementations for those interfaces.

This allows for loose coupling of code because object A no longer needs to be concerned with initializing its own dependencies. Object B decides which implementations to provide to object A based on a configuration or desired behavior.

This is an…

Magento and Adobe Commerce has an outdated js frontend which was modern in 2012 when project was started. The main Magento 2 stack is require.js, jquery, knockout.Js, and a lot of spaghetti code. By the way, developers hate this shame and basically don’t use that and build their own frontend Magento-less solutions using ReactJS or an old Magento 1 approach. For example, Vue Storefront created my Divante and Hyva Teme created by Willem Wigman.

Adobe Commerce has terrible checkout out of the box. Magento Named it a single page application on KnockoutJS but it still requires a lot of backend…

I thought it was obvious that Magento 2 written in a modern like OOP style and uses Java-like approaches is unmaintainable and simply a mess. Magento 2 abuses all possible OOP principles and makes software complex and unmaintainable. Merchants have chosen Magento 2 to solve a few of your basic eCommerce problems. Now they are having 100,500 complex software problems.

“Magento 2 is supposed to make us feel like we’ve built a store on a solid, modern foundation, but from the very beginning it has left us feeling like we’ve built our store on a house of cards.

I feel…

One well knew Fortune 500 brand had an issue with the Adobe Commerce Performance.

Suddenly website response time jumps to 10 seconds for all pages nad one in hour sites went down.

After a bit of debugging, it became clear that Adobe Commerce's shitty code causing this issue.

This observer :

Magento\CustomerSegment\Observer\ProcessEventObserver

Produces harmful queries that killing the RDS MySQL database.