Cloudflare MoQ: Isolated Relays for Media Over QUIC
This article introduces Cloudflare's new API for provisioning isolated Media over QUIC (MoQ) relays, enabling developers to build low-latency, large-scale media applications without managing their own infrastructure. It focuses on the architectural shift from dedicated servers to a global, shared network where relays are logical scopes with fine-grained access controls. This approach simplifies deployment and scaling for real-time applications by leveraging Cloudflare's existing Anycast network.
Read original on Cloudflare BlogCloudflare has enhanced its Media over QUIC (MoQ) offering by introducing a provisioning API that allows developers to create isolated relays. MoQ is an open, publish/subscribe protocol developed by the IETF for efficient, low-latency media delivery over QUIC. Traditionally, MoQ relays would run on dedicated servers, requiring manual scaling and load balancing. Cloudflare's innovation shifts this paradigm by treating a relay as an isolated scope within its existing global Anycast network, rather than a dedicated virtual machine or container.
Architectural Shift: Logical Scopes over Dedicated Servers
Instead of provisioning physical or virtual servers, the Cloudflare MoQ API provisions a logical configuration layer across their global network. This approach provides several architectural benefits:
- Instant Provisioning: Relays are available within seconds as they only involve configuration changes on an already running infrastructure.
- Global Scale by Default: Leveraging Cloudflare's Anycast network, relays are globally distributed from inception, removing the need for developers to manage regional deployments or choose capacity.
- Reduced Operational Overhead: Developers are freed from concerns about server deployment, sizing, load balancing, or managing underlying infrastructure.
- Isolation and Security: Each provisioned relay creates an isolated scope, ensuring that streams, tracks, and objects of one application do not mix with others. This is crucial for multi-tenant applications and security.
Control Plane for Access and Permissions
The provisioning API acts as a control plane for managing these logical relays and their associated access tokens. It separates control-plane operations (relay creation, token issuance) from data-plane operations (media flow). This allows for granular access control:
- Relay Resource: Represents the isolated logical delivery context for an application's MoQ streams.
- Token Resource: Credentials that grant specific operations (publish, subscribe, or both) on a designated relay. Tokens can be scoped, given an expiration, and revoked independently, enabling secure management of publisher and subscriber roles.
System Design Implication
This design pattern demonstrates how a global CDN can abstract away complex infrastructure, offering logical resources and powerful control planes for building distributed systems. The separation of concerns between media transport (MoQ) and access control (API/tokens) is a key architectural decision.