-
Notifications
You must be signed in to change notification settings - Fork 424
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Week-3: Presentation Proposal (#2412)
* Add files via upload * Update README.md * Update README.md
- Loading branch information
Showing
1 changed file
with
27 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,27 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Blue-Green Deployment: Ensuring Zero Downtime in Continuous Deployment | ||
|
||
## Names and KTH ID | ||
|
||
- Hexu Li ([email protected]) | ||
- Tianning Liang ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 3 | ||
|
||
## Category | ||
|
||
- Presentation | ||
|
||
## Description | ||
|
||
|
||
In this presentation, we will explain the **Blue-Green Deployment** strategy used in **Continuous Deployment**. This ensures **zero downtime** during updates by maintaining two identical environments: **Blue (current)** and **Green (new)**. We will cover how traffic can be switched between these environments, ensuring seamless updates and fast rollback in case of issues. The presentation will also include its implementation in **Kubernetes** and its benefits in Long-running systems. | ||
|
||
Relevance: | ||
|
||
Blue-Green Deployment is a key strategy in **Continuous Deployment**, helping teams deliver seamless, risk-free updates and ensuring high availability during deployment. |