Architect overall Waveguide design
- Dominant language
- Go
- Stars
- 40
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Waveguide has a simple architecture focused on inputs, control, and outputs.
* Inputs: A thin layer that translates a specific protocol / technology into RTP packets. Examples: RTMP, FTL, SRT, WHIP, etc.
* Control: A middle layer that handles routing those RTP packets, managing stream state, performing heartbeats to update services & orchestrators.
* Outputs: A thin layer that translates RTP packets into a specified output. Examples: WHEP, HLS, Video Files, etc.
* Services: A service is an external resource that handles authentication, stream metadata, thumbnail serving, and more. An example is Glimesh
* Orchestrators: Routing layer to store what channels are live, and where you need to go to watch them.
This issue involves documenting this architecture, calling out unknowns, and producing artifacts that can be used to help explain Waveguide.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.