How real-dev-squad/skill-tree-backend works
Main System Components
a) External Systems:
• GitHub Authentication
• RDS Backend Service (external dependency)
• Frontend Application
b) Core Application Components:
• Authentication Layer
• API Controllers
• Service Layer
• Repository Layer
• Database Layer
Architectural Patterns to Highlight
The project follows several clear patterns that should be represented:
a) Layered Architecture:
• Controllers (APIs) Layer (apis package)
• Service Layer (services package)
• Repository Layer (repositories package)
• Model Layer (models package)
b) Security Architecture:
• JWT Authentication
• Role-based Access Control
• Custom Security Filters
[Frontend Client] ←→ [Load Balancer/API Gateway]
• ↓
[Authentication Layer]
• JWT Filter
• Security Config
• Auth Entry Point
• ↓
[API Layer]
• Skills API
• Endorsements API
• Health API
• ↓
[Service Layer]
• Skill Service
• Endorsement Service
• Metric Service
• RDS Service (External)
• ↓
[Repository Layer]
• Skill Repository
• Endorsement Repository
• User Skill Repository
• ↓
[Database Layer]
• PostgreSQL (indicated by migrations)
[External Services]
• RDS Backend
• GitHub Auth
Important Details
a) Authentication Flow:
• GitHub OAuth flow
• JWT token validation path
• Role-based access control
b) Data Flow:
• Skill creation/management flow
• Endorsement flow
• User skill status updates
c) Cross-cutting Concerns:
• Exception handling
• Metrics collection
• Logging
Environment Configurations
• Different deployment environments (dev, staging, production)
• Docker container boundaries
Technical Stack Indicators
• Java 17
• Spring Boot
• Maven
• PostgreSQL
• Docker
• GitHub Actions (CI/CD)