Dogfooding at scale: migrating cdnjs to Cloudflare’s Developer Platform
Curated from Cloudflare Blog
When an infrastructure provider claims their own platform is battle-ready, skepticism is healthy. Most internal tooling remains a patchwork of legacy scripts and unoptimized Kubernetes deployments, rarely reflecting the polished architecture marketed to external customers. Cloudflare’s decision to migrate cdnjs, a high-traffic open-source CDN handling billions of daily requests, to their Developer Platform serves as a critical stress test. This move transforms theoretical capacity into observable reality, validating the resilience and scalability of their edge computing stack under genuine load. For SREs and DevOps engineers, the value lies not in the migration itself, but in the resulting visibility into how serverless architectures handle sustained, high-volume traffic without the operational overhead of traditional container orchestration. It demonstrates that modern edge platforms can support mission-critical workloads previously reserved for monolithic systems. Adopting similar internal migration strategies allows teams to identify bottlenecks early and build confidence in their infrastructure choices before committing to large-scale public deployments.
We moved cdnjs, serving 9 billion requests a day, entirely onto Cloudflare's Developer Platform. That means we’re running one of the Internet's busiest open-source CDNs on our own building blocks, and we pushed Workflows and Workers limits higher for everyone.
— Cloudflare Blog