3 ms·
If I started a Twitch (or Discord) competitor today, I would use Janus as a base for web-rtc to share the load https://janus.conf.meetecho.com/ https://janus.co
by olah_1 7y ago
If I started a Twitch (or Discord) competitor today, I would use Janus as a base for web-rtc to share the load https://janus.conf.meetecho.com/ https://janus.conf.meetecho.com/
In fact, Evasyst is a blend of Twitch and Discord and uses Janus for this reason. https://evasyst.com/ https://evasyst.com/
- ec109685 7y agoTwilio is another option to get started since they can handle a lot of the heavy lifting: https://www.twilio.com/video https://www.twilio.com/video
- olah_1 7y agoWhy pay Twilio for web-rtc though? Aren't there enough open source web-rtc wrappers like Janus?
- slimscsi 7y agoYou would look at how much that costs and make a different decision. It can’t scale economically to Twitch size without massive amounts of investment into POPs (source: I built the HLS transcoding stack/infrastructure and HTML5 player at Twitch). A voice only service, sure because it’s 100 times less bandwidth.
- kd5bjo 7y agoGranted, we made the same evaluation about Wowza a decade ago, but it turned out to be useful as a small piece of a large system. Given how much Twitch has grown since then, no off-the-shelf system would be able to handle the scale. A brand-new competitor, though, won’t have to deal with those scaling problems for a while. They have to figure out product-market fit first, which probably can be done off-the-shelf these days. And then they’ll need to figure out how to keep the lights on, which will take a similar amount of engineering work as it did for Justin/Twitch.