Real-time communication: WebRTC protocols and infrastructure
Short answer
Real-time communication is bidirectional exchange of data (audio, video, messages) with sub-second latency. In enterprise, it relies mainly on WebRTC for media and WebSocket for signaling. Video architecture combines SFU, TURN, and API to industrialize these exchanges.
WebRTC vs WebSocket: complementary roles
| WebRTC | WebSocket | |
|---|---|---|
| Transport | Media streams (audio, video) | Text/binary messages |
| Latency | Sub-second | Sub-second |
| Encryption | Native DTLS-SRTP | WSS (TLS) |
| Video usage | Direct transport | Signaling |
| Topology | P2P or via SFU | Client ↔ server |
WebSocket alone does not carry video; WebRTC alone does not handle business logic.
Real-time vs async messaging
| Real-time | Async (email, deferred chat) | |
|---|---|---|
| Latency | < 1–3 s | Minutes to hours |
| Interaction | Synchronous | Asynchronous |
| Protocol | WebRTC, WebSocket | HTTP, SMTP |
| Usage | Video session, support | Email, tickets |
Real-time communication architecture
- Client: browser with native WebRTC;
- Signaling: WebSocket WSS (join, leave, SDP);
- SFU: multi-participant stream distribution;
- TURN: network relay;
- API: programmatic orchestration;
- Webhooks: events to business systems.
→ Video architecture · Video API
Real-time and low latency
Quality is measured in latency:
- < 300 ms: natural conversation;
- 300 ms – 1 s: acceptable for professional video;
- > 3 s: degraded interaction (deferred streaming territory).
Real-time communication and sovereignty
Real-time stacks hosted in France with GDPR framing and open source auditability meet enterprise and public sector requirements.
How does Leagora deliver real-time communication?
Sovereign WebRTC platform, video API, business products for support, meetings, appointments, live. Contact.
FAQ
Is WebRTC the only real-time protocol?
For browser video without plugins, WebRTC is the standard. WebSocket handles coordination and data channels.
Can real-time scale to large audiences?
Interactive sessions use SFU; passive large audiences may combine WebRTC with CDN/HLS hybrid models.
Does real-time require installation?
Browser WebRTC enables no-install guest journeys. See browser-based video comparisons.
Key takeaways
- Real-time = WebRTC media + WebSocket signaling + SFU/TURN infrastructure.
- Sub-second latency is achievable with France-hosted SFU and documented TURN.