How checku-dev/checku-server works
Main Components
a. Client Layer:
• Mobile Application (Android/iOS clients)
• As the entry point for user interactions
b. Server Layer (Spring Boot Application):
• API Gateway/Load Balancer (Nginx)
• Core Application Components divided into domains:
• User Management
• Subject Management
• Notification System
• Bookmark System
• Portal Integration
• Schedule Management
c. External Services:
• Firebase Cloud Messaging (FCM) for push notifications
• University Portal System (integrated via Feign Client)
d. Data Layer:
• MySQL Database (AWS RDS)
• Redis Cache (for portal sessions)
Component Relationships
• Client → Nginx → Spring Boot Application
• Spring Boot Application → AWS RDS
• Spring Boot Application → Redis
• Spring Boot Application → FCM
• Spring Boot Application → University Portal
Detailed Architecture Breakdown
a. Application Layer (organize by domains):
Domain Components:
• User Domain (Authentication/Authorization)
• Subject Domain (Course Information)
• Notification Domain (Alert System)
• Bookmark Domain (User Preferences)
• Portal Domain (University Integration)
• Schedule Domain (Time Management)
• Topic Domain (Notification Topics)
b. Infrastructure Layer:
Infrastructure Components:
• AWS EC2 (Application Hosting)
• AWS RDS (Database)
• Redis (Caching)
• Jenkins (CI/CD)
• Docker (Containerization)
Important Architectural Patterns to Highlight
• Domain-Driven Design (DDD) structure
• Layered architecture (Controller → Service → Repository)
• Aspect-Oriented Programming (AOP) for cross-cutting concerns
• Feign Client for external service integration
• Caching strategy with Redis
• Asynchronous processing for notifications
Additional Elements
• Security layer (Jasypt encryption)
• Error handling flow
• Logging system (with different appenders)
• Health check endpoints
• Docker containerization boundary
• Load balancing with Nginx
Specific Implementation Details
• Interaction between the notification system and FCM
• Portal session management with Redis
• Demonstrate the bookmark and subject tracking flow
• Async notification processing pattern
This system design should effectively communicate how the application handles real-time course registration monitoring, user notifications, and integration with the university's portal system.