Implementation best practices

There are many ways to implement an Adobe Commerce project. The best practices provided in this section describe the way Adobe expects customers and partners to implement specific use cases. These recommendations are designed to help prevent common problems and potential issues related to site configuration and customization, deployment, operations, performance, and upgrades.

These best practices are organized by implementation phase so you can find the recommendations that apply to your use case.

Planning

Planning

Requirements gathering, architectural design, catalog design, project scoping, account provisioning, user access, extension purchasing

Development

Development

Local and staging environment setup, troubleshooting, code management, sprint planning, sprint review, acceptance testing, and customer sign-off

Launch

Launch

Final pre- and post-launch checklist reviews, production deployment, security configuration, service verification, and performance monitoring

Maintenance

Maintenance

Site monitoring, catalog management, indexing, configuration, feature enhancements, bug fixing, managed services, upgrades

What’s new in implementation best practices

This page contains recent changes that we think you’d like to see. We exclude all minor updates, such as copy editing, from this list.

February 14, 2024

Description
Type
Source
Added best practice for upgrading MariaDB to 10.5.1 and later.
best-practices
7199e7 (commit)

January 3, 2024

Description
Type
Source
Added details about the L2 cache memory sizing configuration options for Adobe Commerce on cloud infrastructure.
best-practices
21da4c (commit)
recommendation-more-help
754cbbf3-3a3c-4af3-b6ce-9d34390f3a60