At TADSummit EMEA 2022, Arin and Alberto will give an update on the most popular WebRTC media servers to consider. They will also dive deeper into scalability with topics such as deployment using Kubernetes/Docker, persistence when using multiple SFU/MCU servers, and optimizations available with WebRTC for better performance.
When WebRTC calls are between parties who are not on the same network, have symmetric public-private pairing (NAT), or have firewall restrictions there are a number of protocols that can be used. This post describes relative QoS performance working with no ICE Servers, a public STUN server, and a self-hosted CoTURN server.
In the past, we’ve spoken of three different types of WebRTC application architectures. There’s a new kid on the block, WebRTC Unbundling, which Arin explores here.
TURN is a must for service reliability across firewalls and cross-network. A distributed point of presence setup across geographies can significantly lower the risk of packet loss as opposed to an uncertain dynamic route via the public internet. The WebRTC-CDN service provided by Subspace shows a significant improvement in packet loss, which leads to better stream reception for the remote endpoint.
