This information applies to all cloud releases:

What is done / Migration Steps?

To perform releases, we employ a rolling update strategy. This approach allows us to release new versions of our software applications safely and smoothly with minimal disruption to users. The strategy involves gradually replacing the old instances of the application with the new ones, ensuring minimal downtime and automatic management of the process. Health checks are utilized to monitor the status of the new instances, and if any issues arise, the system automatically rolls back to the previous version. During the update, traffic is drained from the old instances and gradually shifted to the new ones, ensuring a seamless transition for our users. By following this strategy, we can keep our applications up-to-date with the latest features, security patches, and bug fixes while delivering a reliable and uninterrupted experience to our users.

Downtime

There are no downtimes while deploying the update. There is always at least one instance running to prevent downtimes. We release our instances one after another and always wait for the next instance to finish up any jobs or salesforce synchronizations.

Known Risks

When deploying a backend-release, no data is changed. Any errors are restricted to malfunction while using our services, data cannot be lost or corrupted.

Counteractions

If we encounter any errors while deploying the update, we can instantly initiate a complete rollback to the previous version of our backend.
Nonetheless, we have hourly updates of our database.

Roll-Back Strategy

Health checks are utilized to monitor the status of the new instances, and if any issues arise, the system automatically rolls back to the previous version.

Updated August 11, 2023 14:51