How prgrms-web-devcourse/team-darknight-kkini-be works
Main Components
a. Client Layer:
• Frontend Application (React/Next.js based on the frontend repository mention)
• Mobile/Web Clients
b. API Gateway Layer:
• Nginx (as shown in the configuration files)
• Load Balancer
c. Application Layer:
• Spring Boot Application with following core modules:
• Authentication Module (OAuth2.0, JWT)
• User Management
• Crew Management
• Chat System
• Store Management
• Review System
• Notification System
• Proposal Management
d. Data Layer:
• MySQL Database
• Redis Cache
• AWS S3 (for file storage)
e. External Services:
• OAuth Providers (Google, Kakao)
• AWS Services (EC2, S3, CloudWatch)
• Monitoring Systems
Relationships and Data Flow
• Client-to-Server communication via REST APIs
• WebSocket connections for real-time chat
• Database interactions
• Cache access patterns
• External service integrations
Specific Implementation Details
a. Security Flow:
• OAuth2.0 authentication flow
• JWT token management
• Security filters
b. Data Management:
• JPA repositories
• Flyway migrations
• Redis caching
c. Real-time Features:
• WebSocket connections for chat
• SSE for notifications
Architectural Patterns to Highlight
• Domain-Driven Design (evident from the package structure)
• Microservices-ready architecture
• Event-driven architecture (for notifications)
• Layered architecture within each domain
Deployment Components
• GitHub Actions workflows
• Docker containers
• AWS infrastructure
• Nginx configuration
[Client Layer]
• ↓
[API Gateway/Load Balancer]
• ↓
[Application Layer (Spring Boot)]
• ↓
[Data Layer]
• ↓
[Infrastructure Layer]
• Line types (REST, WebSocket, Internal calls)
• Component types (Services, Databases, External APIs)
• Security boundaries
Keep the abstraction level high enough to show the overall architecture while including crucial implementation details that make the system unique, such as the location-based features and real-time communication components.