-
Notifications
You must be signed in to change notification settings - Fork 427
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
|
||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Reducing Downtime with Blue-Green Deployment using Vercel | ||
|
||
## Names and KTH ID | ||
|
||
- Noel Tesfalidet ([email protected]) | ||
- Milad Farahani ([email protected]) | ||
|
||
## Deadline | ||
- Week 3 | ||
|
||
## Category | ||
- Demo | ||
|
||
## Description | ||
This demo will cover the importance of having a deployment strategy and show how | ||
blue green deployment can be achieved on the web hosting platform Vercel (https://vercel.com/). | ||
The demo will entail showing some basic website (Blue environment) and making a small change | ||
to the site (Green environment) during the demo. The new deployment/website will be configured on stage to direct some of | ||
the traffic to the domain to go to the Blue environment and some to the Green environment with no downtime. | ||
|
||
**Relevance** | ||
Blue-Green Deployment is relevant to DevOps because it provides a strategy for seamless | ||
releases with minimal downtime. This is a core objective of DevOps practices. When having | ||
two separate environments, a "Blue" one for the current version and a "Green" one for the | ||
new version, it allows teams to deploy new code with safety. Developers can also test the | ||
code in production and switch traffic between environments with minimal risk. This strategy | ||
reduces the impact of failures and enables quick rollbacks. It also promotes continuous | ||
delivery and deployment, which improves factors such as speed and reliability of software releases. | ||
|