How team-aliens/dms-backend works
High-Level Architecture Components
a) External Layer (Adapters):
b) Application Layer:
• Use Cases (Facade pattern)
• Domain Services
• Domain Models
c) Ports Layer:
• Input Ports (Primary/Driving)
• Output Ports (Secondary/Driven)
Domain Components
Create distinct sections for each core domain:
• Auth (Authentication/Authorization)
• Student Management
• Room Management
• Points Management
• Meal Management
• Notice System
• Study Room Management
• Outing Management
• Volunteer Management
• Notification System
Technical Components
Supporting technical components:
• AWS Services (S3, SES)
• Firebase Cloud Messaging
• Redis
• PostgreSQL Database
• Security Layer (JWT)
• Event System
Flow Representations
• Request flow: Web Adapter → Use Case → Domain Service → Persistence
• Event flow: Domain Events → Event Handlers
• External service interactions
Specific Implementation Details
Annotations showing:
• Kotlin/Spring Boot as the primary technology
• Hexagonal Architecture patterns
• DDD concepts (Aggregates, Entities, Value Objects)
• CQRS pattern (Command/Query separation)
Clean Architecture aspects
• Clear boundaries between layers
• Dependency rules (dependencies point inward)
• How the core domain is isolated
Service Structure
• CheckService
• GetService
• CommandService
• How they interact with Use Cases
Database Interactions
• ERD connection
• How persistence adapters implement ports
Security Flow
• JWT authentication flow
• Authorization checks
• School-specific validations
Remember to use standardized UML or C4 model notation where appropriate, but prioritize clarity and understanding over strict adherence to any particular notation system.