After you create and deploy applications in the Enterprise Distributed Application Service (EDAS) console, you can upgrade the applications. If an upgraded application does not run as normal, you can roll back the application to its previous version. This topic describes how to upgrade and roll back an application.

Upgrade an application

The following table lists the upgrade policies and methods that you can use to upgrade an application in different scenarios.

Upgrade policy Scenario Upgrade method Documentation
Single release The application has a small scale and a simple architecture. After you develop and test a new version, you can directly release the version.
  • Console
  • API
  • Plug-ins or tools
Batch release The application has a large scale and a complex architecture. You can upgrade the application in stages. Only some application instances are upgraded each time until all application instances are upgraded. If an error occurs during a batch release, you can stop the upgrade process and roll back the application. After you fix the error, you can release the application again.
  • Console
  • API
  • Plug-ins or tools
Canary release Before you release a new version of an application, you must test the new version on a small scale. Console Canary release for ECS clusters

Roll back an application

If an error occurs when or after you upgrade an application, you can roll back the application to its previous version. After you fix the error, you can upgrade the application again.

  • If an error occurs when you upgrade the application, stop the upgrade process and roll back the application.
  • If an error occurs after you upgrade the application, roll back the application to its previous version.

For more information, see Roll back an application.