Renaming Calls to Realtime

Author: dcpena

public/realtime/static/realtime-api-2024-05-21.yaml

@@ -229,33 +229,33 @@
   updated: 2023-03-22
 - link: https://github.com/cloudflare/orange
   id: Orange Meets
-  description: Orange Meets is a demo WebRTC application built using Cloudflare Calls.
+  description: Orange Meets is a demo WebRTC application built using Cloudflare Realtime.
   tags: []
-  products: [Calls]
+  products: [Realtime]
   languages: [TypeScript]
   cloudflare: true
   updated: 2024-07-05
 - link: https://github.com/cloudflare/calls-examples/tree/main/whip-whep-server
   id: WHIP-WHEP Server
-  description: WHIP and WHEP server implemented on top of Calls API.
+  description: WHIP and WHEP server implemented on top of Realtime API.
   tags: []
-  products: [Calls]
+  products: [Realtime]
   languages: [TypeScript]
   cloudflare: true
   updated: 2022-06-12
 - link: https://github.com/cloudflare/calls-examples/tree/main/echo
-  id: Calls Echo Demo
+  id: Realtime Echo Demo
   description: Demonstrates a local stream alongside a remote echo stream.
   tags: []
-  products: [Calls]
+  products: [Realtime]
   languages: [JavaScript]
   cloudflare: true
   updated: 2025-05-10
 - link: https://github.com/cloudflare/calls-examples/tree/main/echo-datachannels
-  id: Calls DataChannel Test
+  id: Realtime DataChannel Test
   description: This example establishes two datachannels, one publishes data and the other one subscribes, the test measures how fast a message travels to and from the server.
   tags: []
-  products: [Calls]
+  products: [Realtime]
   languages: [JavaScript]
   cloudflare: true
   updated: 2022-06-04

src/assets/images/calls/video-calling-application.png renamed to src/assets/images/realtime/video-calling-application.png

@@ -0,0 +1,47 @@
+---
+pcx_content_type: get-started
+title: Realtime vs regular SFUs
+sidebar:
+  order: 4
+
+---
+
+## Cloudflare Realtime vs. Traditional SFUs
+
+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.
+
+### The Limitations of Centralized SFUs
+
+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:
+
+* **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.
+
+* **Scalability Concerns:** Scaling a centralized SFU to meet global demand can be challenging and inefficient, often requiring additional infrastructure and complexity.
+
+### How is Cloudflare Realtime different?
+
+Cloudflare Realtime addresses these limitations by leveraging Cloudflare's global network infrastructure:
+
+* **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.
+
+* **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.
+
+## How Cloudflare Realtime Works
+
+### Establishing Peer Connections
+
+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.
+
+### Signaling and Media Stream Management
+
+* **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.
+
+* **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.
+
+### Application-Level Management
+
+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.
+
+## Getting Started with Cloudflare Realtime
+
+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.

src/content/apps/index.yaml

@@ -7,6 +7,6 @@ release_notes_file_name:
 
 import { ProductReleaseNotes } from "~/components";
 
-{/* <!-- Actual content lives in /src/content/release-notes/calls.yaml. --> */}
+{/* <!-- Actual content lives in /src/content/release-notes/realtime.yaml. --> */}
 
 <ProductReleaseNotes />

src/content/docs/calls/index.mdx

@@ -11,25 +11,25 @@ While it is possible to send audio and video over DataChannels, it's not optimal
 
 ```mermaid
 graph LR
-    A[Publisher] -->|Arbitrary data| B[Cloudflare Calls SFU]
+    A[Publisher] -->|Arbitrary data| B[Cloudflare Realtime SFU]
     B -->|Arbitrary data| C@{ shape: procs, label: "Subscribers"}
 ```
 
-DataChannels on Cloudflare Calls can scale up to many subscribers per publisher, there is no limit to the number of subscribers per publisher.
+DataChannels on Cloudflare Realtime can scale up to many subscribers per publisher, there is no limit to the number of subscribers per publisher.
 
 ### How to use DataChannels
 
-1. Create a two Calls sessions, one for the publisher and one for the subscribers.
+1. Create  two Realtime sessions, one for the publisher and one for the subscribers.
 2. Create a DataChannel by calling /datachannels/new with the location set to "local" and the dataChannelName set to the name of the DataChannel.
 3. Create a DataChannel by calling /datachannels/new with the location set to "remote" and the sessionId set to the sessionId of the publisher.
 4. Use the DataChannel to send data from the publisher to the subscribers.
 
 ### Unidirectional DataChannels
 
-Cloudflare Calls SFU DataChannels are one way only. This means that you can only send data from the publisher to the subscribers. Subscribers cannot send data back to the publisher. While regular MediaStream WebRTC DataChannels are bidirectional, this introduces a problem for Cloudflare Calls because the SFU does not know which session to send the data back to. This is especially problematic for scenarios where you have multiple subscribers and you want to send data from the publisher to all subscribers at scale, such as distributing game score updates to all players in a multiplayer game.
+Cloudflare Realtime SFU DataChannels are one way only. This means that you can only send data from the publisher to the subscribers. Subscribers cannot send data back to the publisher. While regular MediaStream WebRTC DataChannels are bidirectional, this introduces a problem for Cloudflare Realtime because the SFU does not know which session to send the data back to. This is especially problematic for scenarios where you have multiple subscribers and you want to send data from the publisher to all subscribers at scale, such as distributing game score updates to all players in a multiplayer game.
 
 To send data in a bidirectional way, you can use two DataChannels, one for sending data from the publisher to the subscribers and one for sending data the opposite direction.
 
 ## Example
 
-An example of DataChannels in action can be found in the [Calls Examples github repo](https://github.com/cloudflare/calls-examples/tree/main/echo-datachannels).
+An example of DataChannels in action can be found in the [Realtime Examples github repo](https://github.com/cloudflare/calls-examples/tree/main/echo-datachannels).