System Architecture
🇰🇷 한국어 버전
Service Composition
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Frontend │────▶│ Backend │────▶│ Worker │
│ │ │ │ │ (Analyzer) │
└─────────────┘ └──────┬──────┘ └──────┬──────┘
│ │
┌──────▼──────┐ ┌──────▼──────┐
│ PostgreSQL │ │ Core │
│ (River Queue) │ (Parser) │
└─────────────┘ └─────────────┘Service Roles
| Service | Role |
|---|---|
| Frontend | Web dashboard |
| Backend | REST API, OAuth |
| Worker | Async analysis worker |
| Core | Test parser library |
Data Flow
User → Enter GitHub URL
→ Backend: Analysis request
→ PostgreSQL (River): Task queue
→ Worker: git clone + parsing
→ PostgreSQL: Store results
→ Frontend: View resultsCommunication Patterns
| Path | Method |
|---|---|
| Frontend ↔ Backend | REST/HTTP |
| Backend → Worker | Message queue |
| Worker → Core | Library call |
Scaling Strategy
- Horizontal scaling of Workers
- Analysis result caching
