Don't Get Locked Into One Provider #cloudarchitecture #webrtc

20 Mar 2026 · 1 min
1:03

In this short talk, the speaker critiques the notion that public cloud alone can meet the demands of large‑scale WebRTC deployments. He highlights the cost and control limitations of major public cloud providers when handling predictable, global traffic. To address this, he proposes a hybrid cloud architecture: run steady, predictable workloads on owned bare‑metal servers or on lower‑tier IaaS providers to gain cheaper, faster, and more controllable infrastructure, while reserving public clouds (AWS, GCP, Azure) as a burst capacity for viral spikes or datacenter outages. This approach improves resilience, avoids vendor lock‑in, and balances private and public resources. He ends by prompting the audience to consider whether they are truly balancing private and public clouds for their media servers or relying on a single provider.

Chapters

More from Tsahi

9:15
youtube.com

After 15 years of WebRTC, here is when I drop peer-to-peer

1mo ago
1:39
youtube.com

Why UDP won the real-time war #programming #webrtc #shorts

1mo ago
1:37
youtube.com

The Difference Between SFU And TURN Servers #WebRTC #RealTimeCommunications

2mo ago
1:43
youtube.com

Why server logs are useless for WebRTC #webrtc #getStats #observability

2mo ago
1:49
youtube.com

How does WebRTC even know a packet was lost?

2mo ago
1:42
youtube.com

WebRTC gives you every tool to watch your calls, then collects nothing

2mo ago
1:40
youtube.com

All green but calls are broken #qoe #dashboards #webrtc

2mo ago
14:03
youtube.com

Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin

2mo ago
1:16
youtube.com

Is your video API vendor ready for AI agents?

3mo ago
1:21
youtube.com

What "$4 per 1000 Minutes" Really Costs You (Video API Pricing)

3mo ago
1:30
youtube.com

How to Read the WebRTC Tools Hub in 90 Seconds

3mo ago
See all content