Even a custom development shop like ours often uses a CPaaS solution when our clients need to get to market quickly or require a large range of communication options within their WebRTC application. Vonage’s comprehensive suite of Communication APIs is a definite go-to for us. We even built it into our own SimplyDoc Telehealth Starter Kit.
When choosing your WebRTC application architecture, there are trade-offs between going with a native application against the standard, an open source media server, or using a commercial CPaaS platform. There are, however, some simple rules you can follow to lead you to the right decision for 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.
Two members of the WebRTC.ventures team, Hamza Nasir and Justin Williams, participated in TADHack 2020. Their hack was to create a CPaaS solution for a more organized and efficient way to handle missed calls when you’re away from work using AI. They came home with the Symbl.ai prize!
