Does WebRTC need a change in governance?
Is it time to change the governance of WebRTC in order to keep it growing and flourishing?
Read MoreS doesn't stand for Simple in WebRTC SFU.
I have noticed recently that more and more companies are attempting the creation of their own SFU. SFU stands for Selective Forwarding Unit, and it is by far the most popular and cost efficient architecture today for multiparty video with WebRTC. With it, all participants send their video to a single entity (usually in multiple resolutions/bitrates), and that single entity decides (selectively) how to route the incoming video to all the participants.
One such popular framework is the Jitsi Videobridge.
Up until today, an SFU for WebRTC was rather simplistic. You had VP8 to contend with as a developer but that's about it. Life was good. You built your service and mostly whined about incompatibility between browsers.
Things have changed.
Here are a few things that you need to take into consideration when you either build your own WebRTC SFU or adopt/acquire one from others:
Like any other technology, once you get down to it, there's more to do than the proof of concept. Consider these aspects at the beginning of your project - and not when you need to seriously rethink your architecture.
Is it time to change the governance of WebRTC in order to keep it growing and flourishing?
Read MoreRTC@Scale is Facebook’s virtual WebRTC event, covering current and future topics. Here’s the summary for RTC@Scale 2024 so you can pick and choose the relevant ones for you.
Read More