Often, platform migrations present challenges, especially in database handling and repository structure. One common issue is database migration, where some databases cannot be directly imported to the cloud. In these cases, our database team supports a smooth transition.

Another frequent issue is the improper handling of Composer and vendor folders, because custom code inside the vendor folder can introduce complications and should be avoided. Ensuring that repository management follows best practices helps maintain compatibility and simplifies future updates.

Key areas for Adobe Commerce project reviews

To maintain security, scalability and performance beyond setups and migrations, several key areas have to be evaluated. Let’s explore them!

• One of the most important things to consider is the Adobe Commerce version that’s in use. If an upgrade isn’t immediately possible, then it’s essential that the latest security patches are applied to maintain system integrity.
• The app code and third-party extensions also require thorough review. The app/code directory is assessed for extensions, ensuring they are managed via Composer whenever possible. If any extension contains custom modifications, they are flagged for further evaluation, as these changes can complicate future upgrades.
• Another area to focus on is the front-end performance. Using Lighthouse, we analyze and address performance bottlenecks that may impact the user experience. For instance, security headers are reviewed to verify that the appropriate configurations are in place, helping us be sure that the project adheres to industry security standards.
• Finally, we also review coding standards and code duplication with the goal of keeping a clean and maintainable codebase. Identifying unnecessary code duplication helps reduce complexity and improve the overall maintainability of the project.

Thoroughly reviewing these key areas helps us maintain a secure, scalable and high-performing Commerce project. Regular evaluations or health checks both prevent potential issues and set the foundation for long-term success, making future updates smoother and more efficient.

Both plugins and preferences play a significant role in the flexibility of an Adobe Commerce project, but they must be implemented correctly. We recommend avoiding around method plugins as much as possible, considering they increase stack traces and negatively impact performance. The only valid use case for an around plugin is when the execution of all further plugins and the original method have to be terminated. In most cases, after method plugins provide a more efficient solution.

On the same note, we also recommend using preferences with caution. Overriding entire methods or classes should be a last resort, since this approach can introduce conflicts and reduce maintainability. Whenever possible, alternative extensibility options such as event observers and plugins should be used instead.