Cloudflare and Akamai Eye MOQ for Edge Media Delivery
Major CDN providers are exploring how MOQ fits into their edge infrastructure, potentially transforming how real-time media is delivered globally.
CDNs and the Real-Time Challenge
Content Delivery Networks have mastered the art of delivering pre-segmented media (HLS, DASH) at scale. But real-time, sub-second delivery is a different beast entirely. MOQ presents an opportunity for CDNs to extend their edge infrastructure into the real-time domain.
Cloudflare's Approach
Cloudflare has been actively participating in IETF MOQ discussions. Their interest is driven by several factors:
- WebTransport support: Cloudflare already supports HTTP/3 and QUIC at the edge, making WebTransport (and thus MOQ) a natural extension
- Edge computing: Cloudflare Workers could potentially run MOQ relay logic at the edge
- Existing media products: Cloudflare Stream could integrate MOQ for low-latency delivery
The company has published research and blog posts exploring QUIC-based media delivery, signaling serious interest in the protocol.
Akamai's Position
Akamai, as the world's largest CDN, has a strong interest in next-generation media delivery:
- Scale: Akamai delivers a significant portion of global internet traffic, including live events
- Low-latency products: They already offer low-latency HLS solutions and see MOQ as the next evolution
- IETF participation: Akamai engineers contribute to MOQ working group discussions
The Integration Challenge
Integrating MOQ into existing CDN infrastructure presents unique challenges:
State Management
Unlike HTTP-based streaming where each request is stateless, MOQ requires persistent connections and subscription state. CDN edge nodes need to:
- Maintain WebTransport/QUIC connections
- Track active subscriptions per connection
- Handle subscription lifecycle (subscribe, unsubscribe, errors)
Caching Model
MOQ's caching model differs from HTTP:
- Objects are cached by track and group, not by URL
- Cache invalidation is based on group boundaries
- Late joiners need access to the latest cached group
Fan-Out
The relay fan-out model maps well to CDN edge-to-origin architecture, but requires:
- Efficient inter-relay protocols
- Smart subscription aggregation (deduplicate upstream requests)
- Graceful handling of relay failures and failover
Timeline
CDN adoption of MOQ is expected to follow this rough timeline:
- 2025: Experimental support in select CDN products
- 2026: Beta programs for early adopters
- 2027+: General availability alongside existing streaming protocols
Impact
When major CDNs support MOQ, it removes the biggest barrier to adoption: infrastructure. Publishers won't need to build and operate their own relay networks. Instead, they'll be able to use the same CDN providers they use today, but with sub-second latency.