|
| 1 | +--- |
| 2 | +pcx_content_type: get-started |
| 3 | +title: Realtime vs Regular SFUs |
| 4 | +sidebar: |
| 5 | + order: 4 |
| 6 | +--- |
| 7 | + |
| 8 | +## Cloudflare Realtime vs. Traditional SFUs |
| 9 | + |
| 10 | +Cloudflare Realtime represents a paradigm shift in building real-time applications by leveraging a distributed real-time data plane. It creates a seamless experience in real-time communication, transcending traditional geographical limitations and scalability concerns. Realtime is designed for developers looking to integrate WebRTC functionalities in a server-client architecture without delving deep into the complexities of regional scaling or server management. |
| 11 | + |
| 12 | +### The Limitations of Centralized SFUs |
| 13 | + |
| 14 | +Selective Forwarding Units (SFUs) play a critical role in managing WebRTC connections by selectively forwarding media streams to participants in a video call. However, their centralized nature introduces inherent limitations: |
| 15 | + |
| 16 | +- **Regional Dependency:** A centralized SFU requires a specific region for deployment, leading to latency issues for global users except for those in proximity to the selected region. |
| 17 | + |
| 18 | +- **Scalability Concerns:** Scaling a centralized SFU to meet global demand can be challenging and inefficient, often requiring additional infrastructure and complexity. |
| 19 | + |
| 20 | +### How is Cloudflare Realtime different? |
| 21 | + |
| 22 | +Cloudflare Realtime addresses these limitations by leveraging Cloudflare's global network infrastructure: |
| 23 | + |
| 24 | +- **Global Distribution Without Regions:** Unlike traditional SFUs, Cloudflare Realtime operates on a global scale without regional constraints. It utilizes Cloudflare's extensive network of over 250 locations worldwide to ensure low-latency video forwarding, making it fast and efficient for users globally. |
| 25 | + |
| 26 | +- **Decentralized Architecture:** There are no dedicated servers for Realtime. Every server within Cloudflare's network contributes to handling Realtime, ensuring scalability and reliability. This approach mirrors the distributed nature of Cloudflare's products such as 1.1.1.1 DNS or Cloudflare's CDN. |
| 27 | + |
| 28 | +## How Cloudflare Realtime Works |
| 29 | + |
| 30 | +### Establishing Peer Connections |
| 31 | + |
| 32 | +To initiate a real-time communication session, an end user's client establishes a WebRTC PeerConnection to the nearest Cloudflare location. This connection benefits from anycast routing, optimizing for the lowest possible latency. |
| 33 | + |
| 34 | +### Signaling and Media Stream Management |
| 35 | + |
| 36 | +- **HTTPS API for Signaling:** Cloudflare Realtime simplifies signaling with a straightforward HTTPS API. This API manages the initiation and coordination of media streams, enabling clients to push new MediaStreamTracks or request these tracks from the server. |
| 37 | + |
| 38 | +- **Efficient Media Handling:** Unlike traditional approaches that require multiple connections for different media streams from different clients, Cloudflare Realtime maintains a single PeerConnection per client. This streamlined process reduces complexity and improves performance by handling both the push and pull of media through a singular connection. |
| 39 | + |
| 40 | +### Application-Level Management |
| 41 | + |
| 42 | +Cloudflare Realtime delegates the responsibility of state management and participant tracking to the application layer. Developers are empowered to design their logic for handling events such as participant joins or media stream updates, offering flexibility to create tailored experiences in applications. |
| 43 | + |
| 44 | +## Getting Started with Cloudflare Realtime |
| 45 | + |
| 46 | +Integrating Cloudflare Realtime into your application promises a straightforward and efficient process, removing the hurdles of regional scalability and server management so you can focus on creating engaging real-time experiences for users worldwide. |
0 commit comments