WebRTC (P2P): компромиссы

Question

Accepted Answer

P2P mesh doesn't scale past few peers; SFU for groups; TURN mandatory cost; WebRTC only when low-latency bidirectional media pays off complexity.

## Разбор

- **P2P mesh N participants = N-1 connections each** — uplink dies ~4–5 people. Group calls → **SFU**: send once, server forwards.
- **Must run/pay TURN.** STUN insufficient — ~15% users fail silently without relay. TURN bandwidth = operating cost.
- **When NOT:** one-to-many broadcast (HLS/DASH); server→client only (SSE/WebSocket).
- **API heavy.** Wrappers (LiveKit, mediasoup) over raw `RTCPeerConnection` for most apps.

## Итог

WebRTC for low-latency bidirectional media; SFU + TURN budget for production; not default broadcast path.