Browse past weeks of engineering reads.
Understanding and analyzing how major global events impact internet traffic patterns across different regions and time zones.
HTTP headers like Set-Cookie and Cache-Control on origin responses can unexpectedly prevent cacheable content from being cached at edge locations, requiring difficult origin-side modifications.
Cloudflare needed to optimize cache tier selection for origins hosted across multiple public cloud providers (AWS, GCP, Azure, Oracle Cloud) to improve cache hit rates and reduce latency.
Workers needed a caching layer directly in front of their entrypoints to reduce origin requests and improve response latency without requiring developers to implement custom caching logic.
When DENIC published invalid DNSSEC signatures for the .de TLD, DNS resolvers like 1.1.1.1 faced a critical decision: reject all .de domain queries due to signature validation failures or serve potentially stale cached responses to maintain availability.
Third-party feature flag services introduce unacceptable latency for applications requiring sub-millisecond flag evaluation at global scale.
AI crawlers were ingesting deprecated and non-canonical content despite soft directives like robots.txt, requiring a way to enforce canonical versions without modifying origin infrastructure.
Web pages are growing larger and slower to load due to increased dynamic content, requiring better compression techniques that can adapt to modern agentic web patterns.
CDN cache systems were designed for human traffic patterns but struggle with the distinct access patterns of AI bot traffic, which now represents over 10 billion requests per week and threatens cache efficiency.
Cloudflare needed to significantly increase edge compute throughput per server but faced a tradeoff where high-core-count CPUs came with smaller per-core L3 cache, risking latency penalties for cache-dependent workloads.