How epicgamesext/pixelstreaminginfrastructure works
Main Components
a) Core Services:
• Signalling Web Server (Cirrus)
• SFU (Selective Forwarding Unit)
• Frontend Applications
• Unreal Engine Instance (external component)
b) Libraries:
• Common Library
• Frontend Library
• UI Library
• Signalling Library
Component Relationships
[Unreal Engine Instance] <--WebRTC--> [SFU] <--WebRTC--> [Frontend Client]
• ^
• [Signalling Server]
• ^
• [Frontend Libraries + UI]
Detailed Component Breakdown
Frontend Section:
[Frontend Implementation]
• TypeScript Implementation
• React Implementation
• Angular Implementation
• Frontend Library
• Input Controllers
• Video Players
• WebRTC Controllers
• UI Library
• Overlays
• Controls
• Settings Panel
Signalling Section:
[Signalling Server]
• WebSocket Handlers
• Player Registry
• Streamer Registry
• Connection Management
SFU Section:
[SFU]
• MediaSoup Integration
• SDP Bridge
• Stream Management
Additional Elements
Include:
• Protocol indicators (WebRTC, WebSocket)
• Port numbers for services
• Container boundaries for dockerized components
• NPM package relationships
Deployment Context
How components can be:
• Containerized (Docker)
• Deployed separately
• Scaled independently
• The modular nature of the system
• Clear separation of concerns
• The central role of the signalling server
• The relationship between libraries and runtime components
Remember to:
• Version compatibility notes
• Security boundaries
• Scalable components
• Document external dependencies