Cloudflare: Real-Time Communications at Scale

> and some higher level libraries for using WebRTC

Not libraries - we’re building APIs that allow you to create rooms/channels, connect participants, manage authn/authz, ingest via non-WebRTC protocols (and still broadcast to participants), and trigger serverless code based on events in those channels.

Those clients will still connect over WebRTC using any browser, native client, or client abstractions you build - one of the best things about WebRTC are its browser APIs and existing set of clients.

In the meantime, we’re launching a “managed TURN” service for teams who already have WebRTC infrastructure but who need help scaling and securing.

(I work at Cloudflare and co-authored the blog)

This is a fairly common definition of real time - not specific to Cloudflare. Two people talking over PSTN/cellular between Sydney and London is >= 250ms in the best case. Participants in the same country obviously won’t see this kind of latency.

TURN (as a protocol) doesn’t change this on its own, but our network backbone is going to help minimize jitter and keep latency as close to optimal as possible.

I would agree (if this is your implication) that this is very different from what we consider “real time” when it comes to control systems and safety systems.

(I’m a co-author of the blog post)

WebRTC Components (TURN) doesn't discriminate being media tracks or data channels, and will relay data channels as well :-)

We also have WebSockets via Cloudflare Workers for layering more complex logic on top: https://developers.cloudflare.com/workers/learning/using-web...