How run1e/striker works
Main Components Identification
The project is a microservices-based application with several key components:
a. Core Components:
• Discord Bot Service (bot/)
• Demo Parser Service (microservices/demoparse/)
• Gateway Service (microservices/gateway/)
• Uploader Service (microservices/uploader/)
• CS:GO Recorder Service (recorders/csgo/)
b. Supporting Components:
• Domain Layer (domain/)
• Message Bus System (messages/)
• Data Access Layer (adapters/)
• Services Layer (services/)
Component Relationships
a. Primary Flow:
Message Bus → Uploader Service
b. External Integrations:
• Bot Service ↔ Discord API
• Adapters ↔ Steam API
• Adapters ↔ FACEIT API
Specific Implementation Details
• Rectangles: Main services
• Hexagons: External APIs
• Blue: Core services
• Green: External services
• Yellow: Message bus
• Gray: Storage/Database
• Red: Critical paths
Technical Stack Indicators
Technology labels:
• Python (Main services)
• Node.js (Demo parsing)
• HLAE/advancedfx (Recording)
• Message broker system
Important Architectural Patterns
• Event-driven architecture (messages/)
• Domain-driven design (domain/)
• Repository pattern (adapters/repo.py)
• Unit of Work pattern (services/uow.py)