How prgrms-web-devcourse/team_bbungcles_devnity_be works
Main Components
a) Client-Side Layer:
• Frontend Application (React/Next.js implied from README)
• CloudFront (Static Resource CDN)
b) API Gateway Layer:
• Nginx (Load Balancer & Reverse Proxy)
• Blue-Green Deployment Configuration
c) Application Layer:
• Spring Boot Application Containers (Multiple instances)
• Core Modules:
• Authentication/Authorization (JWT)
• User Management
• Community Features (Introductions, Gatherings, MapGakco)
• Admin Management
• Media Handling
d) Persistence Layer:
• MySQL Database (RDS)
• S3 Storage (Media files)
e) External Services:
• Slack Integration (for notifications)
• API Integration
Architectural Patterns to Highlight
• Blue for client-facing components
• Green for application services
• Yellow for data persistence
• Gray for external services
• Following patterns:
• MVC architecture (evident from the package structure)
• Repository pattern (shown in data access layer)
• Event-driven architecture (for notifications)
• Domain-driven design (clear from domain package structure)
Key Flows
a) Authentication Flow:
• JWT token generation and validation
• Security filter chain
b) Main Feature Flows:
• User registration with invitation system
• Community interaction paths
• Media upload process
• Location-based service flow
Infrastructure Components
• AWS Services:
• EC2 instances
• RDS database
• S3 storage
• CloudFront CDN
• CI/CD Pipeline:
• GitHub Actions
• Docker containers
• Blue-Green deployment setup
Specific Implementation Details
• Annotations for:
• Cursor-based pagination
• Scheduled tasks
• Caching mechanisms
• Security filters
External Services Layer
Left to Right:
• Core services
• Supporting services
• Monitoring/Logging
Additional Elements
• Numbered sequence flows for key operations
• Scaling points and redundancy
• Monitoring and logging points
• The microservice-like architecture with clear domain boundaries
• The robust deployment strategy with blue-green deployment
• The security implementation with JWT
• The scalability aspects with containerization
• The integration points with external services
Remember to maintain a balance between detail and clarity, focusing on the architectural decisions that make this system unique, such as the location-based services and community features.