There are many different ways to handle the video and audio streams in your WebRTC application. In this post, Arin Sime considers the line of decisions around open source media servers. First, whether to use one at all, as opposed to pure peer-to-peer architecture. Then, whether to choose an SFU or an MCU. The answers, as they usually do, rest in your use case.
In a previous post, we discussed the advent of Microsoft’s new Communication-Platform-as-a-Service (CPaaS) platform, Azure Communication Services. Today, we will cover the basic configuration and elements you need to set up an Azure Communication Service app and get our hands dirty building a Group Video Calling App that can handle up to 50 participants.
Our team at WebRTC.ventures often leverage a Communication-Platform-as-a-Service (CPaaS) in our live video application development. With millions more people working remotely, the CPaaS market is bound to grow. That’s why we were very interested to learn that Microsoft was launching their own CPaaS: Azure Communication Services. Let’s take a look.
The big Video-related announcement at Twilio’s SIGNAL 2020 was their introduction of WebRTC Go, a free entry-level tier for building live video applications. Let’s look at a few takeways about this new offering and the CPaaS market.
