How zibbp/ganymede works
Main System Components
a) Frontend Layer:
• Next.js-based web application (in /frontend)
• User interface components for VOD management, live streams, and chat
• Authentication and user management interfaces
b) Backend Layer:
• Go-based API server (in /cmd/server)
• Worker service (in /cmd/worker)
• Task management system (in /internal/tasks)
c) Database Layer:
• PostgreSQL database
• Entity relationships (defined in /ent)
d) Storage Layer:
• Video storage system
• Temporary storage
• Logs storage
• Configuration storage
Key Interactions and Flows
a) Content Archiving Flow:
Twitch Platform -> Worker Service -> Storage System
• > Chat Processing -> Chat Rendering
• > Video Processing
b) User Interaction Flow:
User -> Frontend -> API Server -> Database
• > Video/Chat Playback System
Architectural Patterns
Patterns:
a) Microservices Architecture:
• Server service
• Worker service
• Frontend service
• Database service
b) Task Queue System:
• Task distribution
• Queue management
• Task execution flow
Integration Points
External integrations:
a) Authentication:
• Local auth system
• OAuth/SSO integration
• Twitch API integration
b) Content Sources:
• Twitch VOD API
• Twitch Live Stream API
• Chat data sources (BTTV, FFZ, SevenTV)
Specific Implementation Details
Technical components:
a) API Layer:
• HTTP transport (/internal/transport/http)
• WebSocket connections for real-time features
• API endpoints structure
b) Data Processing:
• Video processing pipeline
• Chat processing and rendering
• Storage management