Distributed Readings

Enabling AI agents to autonomously conduct financial transactions and verify their identity while accessing APIs and content across the web within secure boundaries.

Organizations need a safe, extensible way for all employees to build applications and automate work while securely accessing internal systems without requiring deep infrastructure expertise.

Enterprises needed a unified platform that could provide both Secure Access Service Edge (SASE) and Security Service Edge (SSE) capabilities to protect users and data across distributed networks and edge locations.

Enabling AI agents to interact with existing websites without requiring API modifications or changes to origin infrastructure.

How to safely enable engineering teams to leverage AI tools while maintaining security and controlling access across distributed work environments.

AI agents need a scalable, cost-effective browser environment that can run stateless in cloud infrastructure rather than managing traditional browser instances.

Building scalable CI/CD infrastructure that can handle millions of repositories without requiring users to manage complex YAML configurations or maintain separate CI/CD platforms.

How do you securely grant task-scoped access to autonomous agents while preventing privilege escalation and unauthorized access to sensitive resources?

Managing the operational overhead of AI agents that generate code faster than human teams can review, test, deploy, and maintain it in production environments.

Making MCP (likely Cloudflare's control plane protocol) efficiently executable on edge workers while maintaining state management across distributed edge locations.

AI agent infrastructure needed to scale horizontally and support long-running interactive tasks without being constrained by stateful architecture patterns.

Real-time AI agents with long-lived stateful bidirectional streams cannot be effectively load-balanced using traditional request-response metrics because server capacity is obscured by the nature of continuous conversations.

How to efficiently rank ads at scale by leveraging temporal signals from user action sequences rather than relying on static, manually engineered sparse features across billions of daily interactions.

Meta needed to double the training efficiency of GEM, its LLM-scale ads foundation model, while scaling training compute 4x across thousands of GPUs without proportional increases in training time and cost.

Netflix needed to efficiently query billions of nodes and edges in a real-time distributed graph while maintaining low latency and high availability across their microservices ecosystem.

Providing users with the ability to create isolated, controlled Media over QUIC (MoQ) relays with granular permission management for publishers and subscribers.

Migrating a massive open-source CDN serving 9 billion requests per day from legacy infrastructure to Cloudflare's own Developer Platform while maintaining reliability and performance.

Cloudflare needed to track, measure, and analyze Internet disruptions caused by natural disasters, government-mandated shutdowns, and DNS infrastructure events to understand their global impact on connectivity.

Ensuring secure authentication between Cloudflare's edge servers and customer origin servers remains viable against future quantum computing threats.

Cloud infrastructure was designed for human-browser interactions, but now needs to support autonomous agents with different requirements for storage, execution, and security.

Engineers need a systematic way to diagnose performance bottlenecks in TPU-based machine learning workloads to understand whether they are constrained by compute, memory, or network resources.

Netflix needed to simplify their complex, hand-crafted recommendation system with thousands of features and specialized architectures to make it more maintainable while leveraging large language models.

Netflix needed to accurately model and track heterogeneous device capabilities across millions of devices to determine which features and content types each device could support.