[Wallet Messenger Service] Wireframe, ERD, API, Branch Strategy
This post was migrated from Tistory. You can find the original here.
An MSA-based dues management messenger service that handles heavy traffic
2023.07.31 - [Project/Dues Management Messenger Service] - Messenger service project ERD, API design
I got feedback that it’s hard to find and improve performance bottlenecks in live audio/video, so I changed the plan.
The messenger and the rest of the goals stay the same, but I’m dropping live audio/video and adding features related to group/personal accounts, similar to KakaoBank.
Wireframe
ERD
The ERD went through so many edits that the relationships aren’t easy to follow at a glance anymore. I’ll need to clean it up later.
API
https://github.com/innovationCamp/swagger
Copy the contents of the yaml file from GitHub, paste it into the Swagger editor, and you can view the API.
Just paste it into the editor on the left.
Branch Strategy
- master
- release/vX.X
- develope
- feature/feature-name
I plan to go with these four branch types.
Work happens on feature/feature-name, then gets PR’d into develope.
The contents of develope get PR’d into release/vX.X, and any deployment-related issues get resolved there.
Once all issues are resolved, release/vX.X gets merged into both master and develope.
master is managed with tags.