Default listening ports for your protocol are mostly useless. If you want to deploy in production TURN, SIP, MQTT or anything else thing of 443.
If you plan on implementing a one-to-many WebRTC broadcast scenario, then be prepared to install and maintain media servers to make this happen.
There are certain mistakes that I see people repeat when developing their WebRTC Applications. I want to go over them, so you don’t repeat them.
AWS DeepLens is a new product for developers that is going to change the way we think and architect machine vision related applications.
WebRTC can be used for calls in any group size. The larger the group the more energy you’ll need to put to your architecture and media server technology.
WebRTC adapter.js is a module you should be using in your WebRTC application. The reason? It makes developing with WebRTC for multiple browsers easier.
What’s in a WebRTC API Platform and what makes it different from the classic CPaaS? Here are my thoughts as I prepare to update my report.
There are different ways to explain how WebRTC works. This is my attempt at a WebRTC 101 article that covers it from all angles.
Jitsi videobridge is a popular media server for WebRTC and it is going some interesting changes recently. Here’s a summary of where we’re at.