Member-only story
AWS Deployment Strategies
There are some strategies that you can adopt to deploy your application, the deployment strategies depend on the business model and organization goal.
Well, first of all, when you are choosing your deployment strategy, you should take into consideration the following topics:
- Deployment time;
- Zero Downtime (Yes/No);
- Rollback;
- Extra costs;
- Reduction in current capacity;
Deployment strategies
- In-Place Deployments
- Blue/Green Deployments
- Canary Deployments
- Linear Deployments
- All-at-once Deployments
In-Place Deployments
Updates the application version without replacing any infrastructure components. Basically, all the instances are stopped, and then the latest version is installed.
Disadvantages
- Application availability is affected;
- Rollback (You need to install again the old version);
Advantages
- Do not need new infrastructure;
- Minimizes infrastructure costs and management overhead;
More details can be found here.
Blue/Green Deployments
In this strategy, you have two separate but identical environments (Environment Blue and Green).
Environment Green: running current application version;
Environment Blue: running the new application version;
After the green environment is ready and tested, production traffic is redirected from blue to green. If any problem is found, you can redirect the traffic to the blue environment again.
Disadvantages
- Deployment time;
- Extra cost;
Advantages
- Application availability is not affected;
- Reduces deployment risk (easy rollback, just need to swap URL);
- Zero downtime;
