How realfascinated/scoresaber-reloaded works
Main Components
Frontend Layer:
• Next.js Website Application (/projects/website)
• Desktop Application (Tauri-based) (/projects/desktop)
• User Interface Components (React components)
Backend Layer:
• Backend API Server (/projects/backend)
• WebSocket Services (for real-time scores)
• Controllers and Services
• Bot Integration
Data Layer:
• Database Systems (implied by database utilities)
• Caching System
• MinIO Storage (for assets/images)
External Services Integration:
• ScoreSaber API
• BeatLeader API
• BeatSaver API
• Steam Integration
[Client Layer]
• Web Application (Next.js)
• Desktop App (Tauri)
• Overlay System
[API Gateway/Load Balancer]
[Backend Services]
• Authentication Service
• Player Service
• Score Service
• Leaderboard Service
• Statistics Service
• Playlist Service
• Image Service
• Bot Service
[Data Layer]
• Cache Service
• Database
• MinIO Storage
[External Services]
• ScoreSaber API
• BeatLeader API
• BeatSaver API
• Steam API
Key Relationships to Highlight
• Bidirectional communication between frontend and backend using REST APIs
• WebSocket connections for real-time score updates
• Caching layer interaction with external APIs
• Data flow between services and storage systems
Implementation Details
• Clear component boundaries
• Service interaction patterns
• Scaling points
• Security boundaries
Additional Elements
Annotations for:
• Docker container boundaries
• GitHub Actions deployment flows
• Caching strategies
• Data collection mechanisms
• Score processing pipeline
This system design should effectively communicate the complex architecture while highlighting the scalability and real-time nature of the application.