Skip to content

Commit

Permalink
Merge pull request #70 from gdsc-ssu/seohyeon/week22
Browse files Browse the repository at this point in the history
[week22] AWS CI/CD
  • Loading branch information
candosh authored Sep 8, 2024
2 parents 63d2fd6 + 2e05456 commit 8a37d76
Show file tree
Hide file tree
Showing 15 changed files with 288 additions and 0 deletions.
254 changes: 254 additions & 0 deletions AWS/CICD/CICD란?.md

Large diffs are not rendered by default.

Binary file added AWS/CICD/img/CICD-EX-1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-10.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-11.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-12.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-13.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-6.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-7.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-8.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added AWS/CICD/img/CICD-EX-9.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
34 changes: 34 additions & 0 deletions review/week22/최서현.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# API Gateway

API Gateway란 규모에 상관없이 API 생성, 유지 관리, 모니터링과 보호를 할 수 있게 해주는 서비스이다.
말 그대로 Client에서 server로 통신할 때 사용하는 많은 api들의 대문(게이트웨이)과 같은 역할을 한다고 보면 된다.
즉, API가 지나가는 통로인 셈이다.

# CICD

이 부분은 워낙 쉬웠었다.

# 롤링 배포 블루그린 배포

이 부분에 대해 생각보다 다들 질문을 많이 준 거 같아서 자세히 알아 보겠다!

무중단 배포 방식에 일종으로 Rolling / BlueGreen / Canary가 있다.

책에서는 롤링과 블루그린 배포가 있었는데, 카나리? 배포 방식도 있었다.

> 💡 여기서 잠깐! 무중단 배포란?
> 다운타임을 최소화 혹은 없도록 하는 배포 방식을 무중단 배포(Zero-downtime deployment라고 한다.
그래서 각각이 무엇인지?

### Rolling

롤링 배포는 서버 그룹을 점진적으로 교체하면서 새 버전의 애플리케이션을 배포하는 방식이다. 하나의 서버나 인스턴스를 새 버전으로 교체한 후, 안정성을 확인한 뒤 다음 서버를 교체한다. 기존 서버와 새 서버가 동시에 작동할 수 있어 다운타임이 적다.

### BlueGreen

블루그린 배포는 두 개의 환경(Blue와 Green)을 사용하는 방식이다. 기존 서비스(Blue)가 운영 중인 상태에서 새로운 버전(Green)을 배포하고, 새 버전이 안정적임이 확인되면 트래픽을 새 버전으로 전환한다. 기존 버전은 유지되어 언제든지 롤백이 가능하다.

### Canary

카나리 배포는 새 버전을 일부 사용자에게만 배포해 안정성을 검증한 후 점진적으로 전체 사용자에게 배포하는 방식이다. 위험을 최소화하면서도 새로운 기능을 빠르게 도입할 수 있는 전략이다.

0 comments on commit 8a37d76

Please sign in to comment.