6. Choose a Streaming Service
docker-rtmp-multistream supports multiple streaming destinations with different performance characteristics.
6.1 Supported Services
| Service | Pattern | CPU Usage | Bandwidth | Quality Control | Best For |
|---|---|---|---|---|---|
| Twitch | Conditional¹ | Minimal/High | High/Moderate | Passthrough/Full control | Partners: max quality. Non-partners: optimization |
| YouTube | Simple Relay | Minimal | High | Source passthrough | Maximum quality, leveraging YouTube's re-encoding |
| Archive | Recorder² | Minimal | None (disk I/O) | Source passthrough | Local backup, video on demand (VOD) creation |
¹ Twitch pattern depends on TWITCH_PARTNER setting - see Twitch Configuration
² Archive is not a relay. It records every stream the relay application receives to disk, with no re-encoding. See Archive Service.
6.2 Service Patterns
Destination services use one of two architectural patterns: Simple Relay (direct forwarding) or Transformer (FFmpeg re-encoding). Archive is a recorder and uses neither.
For a detailed comparison of these patterns, see Service Patterns Reference.
6.3 Adding Custom Services
Want to add support for another streaming platform? See the Add a Streaming Service.
6.4 See Also
- Service Patterns Reference - Detailed comparison of architectural patterns
- Architecture - Technical system overview