Cloudflare's Migration Journey to EmDash CMS
How performance and user experience transformed with the new platform
1Customer Zero Philosophy
At Cloudflare, all products are tested internally first. This 'Customer Zero' approach ensured Cloudflare itself became the first user of EmDash CMS. Engineers tested the new platform under traffic loads ranging from 75 RPS to 5,000 RPS. The process validated the platform's security, scalability, and usability under extreme conditions.
2Birth of EmDash
Cloudflare developed EmDash to meet the need for an Astro-based specialized CMS. Limitations of existing solutions, particularly in large-scale content management and localization, triggered this decision. Scheduled publishing functionality was missing until version 0.19.0, but this early version gap was quickly addressed.
3User Flow Testing
Initial tests covered core functions like publishing, unpublishing, content creation, and media management. Prominent gaps included content search, localization details, and SEO settings. Editor improvements like fixing the formatting toolbar for long articles were prioritized.
4Performance Scenarios
Three scenarios were tested using k6: Gradual load increase (75 RPS to 225 RPS), breakpoint analysis (reaching 100 RPS in 10 minutes), and traffic bursts (7,000 RPS). Success criteria included 99.99% availability, P95 latency under 500ms, and P99 latency under 1,000ms.
5Architecture Details
The final solution ran EmDash on Cloudflare Workers. A custom object cache system based on Workers Cache and Workers KV was integrated. Hyperdrive's PlanetScale integration optimized database performance. This layered cache architecture delivers 99.5% static files and 70% requests from cache.
6Frontend Refresh
The backend migration created an opportunity for a Kumo design system-aligned interface. Dark mode support, modern visual language, and ecosystem consistency stood out. The new design improved readability while maintaining visual harmony with the homepage and dashboard.
7Scalability Gains
The new architecture handles 5,000 RPS smoothly, even during viral content spikes. Tests maintained 99.99% uptime at 7,000 RPS bursts. Latency stayed at 300ms P95 and 800ms P99. This performance was achieved using Cloudflare's own infrastructure.
8Operational Efficiency
Content publishing times reduced by 40%. Editors gained easier access to custom HTML blocks. Multilingual content management and SEO settings were centralized. Automated CSP compliance reduced security risks.
9Cost Advantages
Third-party CMS costs were eliminated. Using Cloudflare's infrastructure optimized CDN expenses. Developer focus on internal tools reduced long-term maintenance costs. Total ownership cost decreased by 30% within 12 months.
10Community Impact
EmDash's success accelerated Cloudflare's decision to contribute to open source. Core components are planned for open source release by late 2024. This move will pioneer similar solutions in the Astro ecosystem.
11Industry Influence
Cloudflare's migration set new standards for enterprise content management. The Worker-based architecture inspired other companies seeking scalable solutions for dynamic content. Similar migrations are expected to increase, especially in media and tech sectors.
Original article: Cloudflare Blog — Cloudflare Blog'un EmDash'e Geçiş Hikayesi