CDNJS's Cloudflare Dev Platform Leap

From Legacy to Leading-Edge

This article offers a compelling case study of Cloudflare's internal 'dogfooding' success, demonstrating the maturity and capabilities of their Developer Platform by migrating a critical, high-traffic service like cdnjs. The detailed breakdown of the previous architecture's pain points—particularly observability and the "split-brain" storage issue—effectively justifies the migration. The new architecture, leveraging R2 for source of truth, KV for metadata, and Workflows for orchestration, represents a significant step forward in managing complex, event-driven pipelines. The article thoughtfully addresses how the platform grew to meet cdnjs's specific needs, including raising platform limits like subrequests per Worker invocation and Workflow steps, which benefits all users. The focus on immutability, SRI hashes, and open-source principles also addresses modern supply-chain security concerns, making cdnjs a more robust and trustworthy resource. The potential for future enhancements, like serving native ES modules, hints at the platform's adaptability.

However, while the migration is presented as a success, a deeper dive into the cost implications of this new architecture, especially concerning R2 storage and Workers execution, would have been valuable for a developer audience considering similar migrations. The article touches on the compression container but acknowledges the ongoing work to stream this logic to Workers, suggesting that some performance optimizations might still be in progress. Furthermore, the article highlights the LLM dependency for cdnjs traffic, which is an interesting observation but could be further explored in terms of how this trend might impact CDN usage and infrastructure planning in the future. The reliance on a separate DigitalOcean Spaces for disaster recovery, while a pragmatic solution, also indicates that Cloudflare's native offerings might still have gaps for certain edge-case resilience requirements, though this is clearly a transitional phase.

Key Points

• cdnjs, a critical open-source CDN serving 9 billion requests daily, has migrated exclusively to Cloudflare’s Developer Platform.
• The migration was driven by internal development pain points, particularly in observability and the complexity of the previous multi-cloud/VM architecture, rather than performance issues.
• The new architecture leverages Cloudflare Workers, Workflows, R2, KV, Queues, and Containers, with R2 as the primary source of truth for file content and KV for metadata.
• Cloudflare's Developer Platform evolved to meet cdnjs's needs, including raising platform limits for subrequests and Workflow steps.
• The migration addressed supply-chain security concerns by maintaining immutability and SRI hashes.
• Future possibilities include transforming packages for native ES module delivery.

---

📖 Source: Dogfooding at scale: migrating cdnjs to Cloudflare’s Developer Platform