https://github.com/zkfmapf123/eventbridge-architecture

event bridge study
https://github.com/zkfmapf123/eventbridge-architecture

Last synced: 3 months ago
JSON representation

event bridge study

• Host: GitHub
• URL: https://github.com/zkfmapf123/eventbridge-architecture
• Owner: zkfmapf123
• Created: 2024-05-12T12:46:09.000Z (about 2 years ago)
• Default Branch: master
• Last Pushed: 2024-05-19T15:40:55.000Z (about 2 years ago)
• Last Synced: 2025-01-13T09:38:23.080Z (over 1 year ago)
• Language: HCL
• Size: 1.29 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# EventBridge Architecture

## ECS Internal Service

![eda-1](./public/3.png)

## ECS Service use Event Bridge

![eda](./public/1.png)

## Progress... (테스트때문에 service destory만 진행함)

- [x] vpc, sqs

- [x] ecs (blue, green, purple)

    - [x] terraform cd

- [ ] api-gateway

- [ ] event bridge use SQS

    - [ ] purple -> blue

    - [ ] green -> blue

    - [ ] blue -> purple

    - [ ] blue -> green

## Desc

- Service

    - Blue

    - Purple

    - Green

- 내부 Internal 통신이 아닌, EventBridge 기반 통신

- EventBridge Role Based 기반으로 Service 팀내에서 관리 가능하도록 구성

- Rule 한개당 대상은 1개로 유지 (Best Practice)

- DLQ 큐는 Service Context 당 1개로 유지

## 1. API Gateway (이건 테라폼으로 안함...)

![2](./public/2.png)

- /blue/{proxy+}

    - http://[BLUE_ALB_DNS]/{proxy}

- /green/{proxy+}

    - http://[GREEN_ALB_DNS]/{proxy}

- /purple/{proxy+}

    - http://[PURPLE_ALB_DNS]/{proxy}