website logo
Sign Up PricingApp Templates
⌘K
🚀Getting started
Create an account in Microtica
Create an application from template
Import an existing application
Scaling Applications in Microtica
Assign a Custom Domain
⏰Changelog
📚Ready-to-use Templates
Strapi Serverless
Medusa Server
Appwrite
SPA on CloudFront
Amazon EKS
Node.js
n8n Workflow Automation
Next.js
🤖Migrate to Microtica
Migrate from Heroku to AWS
🚦Pipelines
Pipeline Syntax
Steps
Stages
Artifacts
Variables
↩️Automated Rollbacks
🔗Integrations
Connect an AWS account
Connect an Existing Kubernetes Cluster
Connect a Container Registry
⚙️Project Settings
Manage teammates
Manage pricing plan and billing
Docs powered by archbee 

Automated Rollbacks

8min

Automated rollbacks in Microtica provide a reliable and efficient mechanism to revert to a previous stable state in case of deployment failures or issues encountered during the cloud release process. This documentation will guide you through the steps to utilize automated rollbacks in Microtica.

microtica automated rollbacks


Prerequisites

Before proceeding with automated rollbacks, ensure that you have the following prerequisites:

  • A Microtica account.
  • A Git Account (GitHub, Bitbucket, GitLab, or CodeCommit).
  • An AWS account connected to the Microtica platform with appropriate permissions.
  • A configured Microtica project with a deployment pipeline set up.

Enabling Automated Rollbacks

Automated rollbacks are available to all users of the platform without any setup requirements.

Utilizing Automated Rollbacks

As automated rollbacks are enabled for any pipeline, the process of utilizing rollbacks during production deployments becomes straightforward. Here's how to use automated rollbacks in Microtica:

Step 1: Initiate a Deployment

Trigger a deployment using the configured pipeline. You can do this manually from the platform's UI or with a git push to the configured branch. Microtica will execute the deployment steps, including building, testing, and deploying the code changes to the environment.

Step 2: Monitoring the Deployment

During the deployment process, closely monitor the pipeline's progress and the health of the deployed infrastructure. Microtica provides real-time visibility into the deployment status, logs, and metrics.

Step 3: Detecting an Issue

If any critical issue or failure occurs during the deployment, Microtica's monitoring systems will identify the problem and trigger an automated rollback.

Step 4: Rollback Process

Once a rollback is triggered, Microtica will automatically initiate the rollback process. This involves reverting the deployment to a previous stable version, ensuring that the production (or non-prod) environment is restored to a working state.

Step 5: Verification and Troubleshooting

After the rollback, verify that the infrastructure is functioning correctly in the restored state. Conduct troubleshooting if necessary to identify the root cause of the issue encountered during the deployment.

By following the outlined steps, you can confidently utilize automated rollbacks in Microtica to quickly recover from deployment failures and ensure the stability of production environments. This feature contributes to a robust and efficient deployment process, minimizing downtime and reducing the impact of potential issues on your applications.

Updated 19 May 2023
Did this page help you?
Yes
No
PREVIOUS
Variables
NEXT
Integrations
Docs powered by archbee 
TABLE OF CONTENTS
Prerequisites
Enabling Automated Rollbacks
Utilizing Automated Rollbacks
Step 1: Initiate a Deployment
Step 2: Monitoring the Deployment
Step 3: Detecting an Issue
Step 4: Rollback Process
Step 5: Verification and Troubleshooting