Best practices for upgrading
This topic lists the actions you should take to manage the complexity of upgrading ÃÛ¶¹ÊÓƵ Commerce projects. Your team should be thinking about upgrades from the moment your project development starts and continue through each release. By following these best practices, the upgrade process will be much easier, faster, and cheaper.
What impacts an upgrade?
It is important to understand the variables that determine the complexity of an upgrade. You must consider these variables at the beginning of each project–not just when is time to upgrade. The development of a project is key to ensure that future upgrades are be smooth and that you are able to control the required effort to complete them.
The level of effort to upgrade your ÃÛ¶¹ÊÓƵ Commerce instance depends upon these factors:
-
How did you build your site? The amount of custom work and the number of installed third-party modules strongly affects the complexity of an upgrade. The quality of the custom work and modules can determine whether an upgrade goes smoothly.
-
Are you skipping multiple releases? Skipping releases makes the next upgrade more complex, upgrading from consequent versions makes the process easier and cheaper.
-
What type of upgrade are you performing? An upgrade to a minor release (from 2.3.x to 2.4.0, for example) is more extensive than an upgrade between patch releases (such as from 2.4.2 to 2.4.3). Security upgrades are the easiest type to implement.
Best practices for planning upgrades
If you are working on a project that is already in production, upgrades are an opportunity for you to improve the quality of your code and customizations, and to optimize for future upgrades. The time you invest today is time saved in the long term.
If you manage multiple sites for different merchants, the best approach is to have a base instance with the main features and customizations you normally use. Use this base instance as your testing site for completing an upgrade and then do it on others. This practice gives you the flexibility to reuse customized modules for different customers and simplify upgrades across projects.
If your project is live, we suggest you run an audit to determine its quality, and understand how you can improve it to make upgrades more efficient.
Developing with upgrades in mind
From the moment you start working on a project, you should consider how future upgrades will be impacted by your current work. Always follow ÃÛ¶¹ÊÓƵ Commerce development best practices as described here:
Begin adopting the ÃÛ¶¹ÊÓƵ Commerce Extensibility platform, if you have not done so already. The platform allows you to efficiently customize processes, integrate systems, and deploy new capabilities while maintaining SaaS-like upgradeability. Its features include:
-
UI Extensibility. Extend and evolve your storefront independently of your backend and middleware using .
-
API Extensibility. Use to extend Web API layer by evolving the graph data model and executing lambda functions directly from the graph layer.
-
ÃÛ¶¹ÊÓƵ I/O middleware and services. Connect your systems with ÃÛ¶¹ÊÓƵ Commerce using ÃÛ¶¹ÊÓƵ’s middleware and a suite of app connections built on . In addition, you can extend core platform capabilities by overwriting the default behavior with your own business logic that runs on ÃÛ¶¹ÊÓƵ I/O.
Planning upgrades
As we continually expand the capabilities of ÃÛ¶¹ÊÓƵ Commerce, it is critical that you develop on the latest available release and define an upgrade strategy into your project plans. Doing so helps you remain secure, compliant, and up-to-date on the latest enhancements that allow you to grow sales faster, operate more effectively, and stay ahead of your competition now and into the future.
To help you plan and budget for upgrades, you should monitor our release schedule. Plan upgrade tasks within your team’s backlog ahead of time. Aim to complete this work with GA.
-
Use the pre-release version to learn about each new release. Pre-release is General Availability code that is available to ÃÛ¶¹ÊÓƵ Commerce merchants and all partners two weeks before General Availability. If you have multiple stores, use the pre-release on your base store and verify that your custom modules and themes are compatible with it.
-
Review the for ÃÛ¶¹ÊÓƵ Commerce to help you plan for your upgrade.
-
Plan for upgrades at the beginning of the year. You must book a budget and resources to complete each upgrade. Remember, the upgrade effort might vary significantly from project to project. Use your experiences and knowledge to make a plan as accurate as possible.
-
If your upgrades are taking more effort than what we describe here, we recommend you audit your project and make adjustments to your environment to reduce the long-term maintenance.
Performing upgrades
Upgrades should be done on regular basis, and under a predefined budget. We recommend scheduling pre-approved upgrades at the beginning of the year to ensure upgrades are planned and completed on time.
Assess the work to be done for upgrading:
-
Review the release notes to understand the scope and impact of the new version.
-
Use the Upgrade Compatibility Tool to identify potential problems that must be fixed in your custom code before attempting to upgrade to a newer version.
-
If you are using third-party extensions, validate their compatibility with the target version you are planning to upgrade to.
Post-upgrade testing
Testing is the phase of an upgrade that requires the most time. As a result, this process should be as automated as possible. You can benefit from using the core testing tools. The provides details.
Use a staging environment to test and validate your upgrade before moving to production.
Make use of a maintenance page. Preparing this page in advance allows you to communicate with your customers, notifying them that work is happening in the background. This page should be visible for a few minutes, but if there is a problem, you might need to use it longer. Having the appropriate content and design for your maintenance page gives your users a good experience even when your store is not available.