Read what ships.

01Cloudflare · architecture

Origin Range Requests: Serving large files without range-request tuning

Cloudflare replaced a legacy, fixed-size range caching design that suffered from bandwidth waste and memory pressure with a Pingora-based chunk coordinator. The new implementation dynamically combines cached chunks and aligned origin fetches to serve range requests accurately without manual tuning. This approach cut p99 time to first byte in half for R2 storage and reduced tiered cache traffic by six percent.

DEPTH ■■■■■8 min read2 days ago

DatabasesPerformanceRedis

Sign in to save and rate

02GitHub · architecture

The bridge to agent-scale Git infrastructure

GitHub faced infrastructure capacity limits and a 25ms cross-region network round trip when migrating repositories to Azure. The team changed the storage quorum from repository-wide locks to per-reference serialization and introduced ephemeral virtual replicas backed by object storage. This raised write throughput, prevented slow replicas from blocking traffic, and decoupled read scaling from the write quorum.

DEPTH ■■■■■8 min read4 days ago

Infrastructure

Sign in to save and rate

03Cloudflare · architecture

Bringing post-quantum cryptography to geographically fenced key management

Cloudflare introduced a post-quantum geographically restricted key manager in closed beta to enforce data sovereignty and protect customers against harvest-now-decrypt-later attacks. The team implemented a hybrid ML-KEM-768 and X25519 cryptographic design that separates globally distributed wrapped private keys from regionally restricted root keys. This ensures that decryption keys are only accessible within authorized geographical boundaries and fails closed if validation fails.

DEPTH ■■■■■12 min read2 days ago

Security

Sign in to save and rate

04Go · performance

Better HTTP/1 connection reuse

Failing to read an HTTP/1 response body completely prevents connection reuse, forcing clients to repeatedly pay the high cost of TCP and TLS handshakes. While developers previously had to implement complex manual body-draining logic, Go 1.27 introduces automatic asynchronous response draining in the net/http package. This improvement allows developers to simply close response bodies without worrying about connection pooling performance.

DEPTH ■■■■■7 min read11 days ago

Sign in to save and rate

05GitHub · architecture

From 2,500 requests to 24: Rebuilding star history without the stargazers

GitHub faced abuse and performance issues because tools were scraping user identities to reconstruct repository star history. The engineering team collaborated with maintainers to build a purpose-built aggregate endpoint that returns daily star counts without identities and filters by time before aggregation. This reduced request volume from thousands to a few dozen and eliminated heavy database scans.

DEPTH ■■■■■8 min read11 days ago

Microservices

Sign in to save and rate

06Cloudflare · performance

Cutting our inference bill by 68% by being obsessive about optimization

An engineering team investigated a steady rise in AI code review costs and found that cache misses and redundant model calls were driving up expenses. By restructuring system prompts to enable cross-repository prompt caching, eliminating wasted tool calls, and switching to more efficient models, the team cut inference costs by 68% while also significantly improving review latency.

DEPTH ■■■■■15 min read6 days ago

Machine Learning

Sign in to save and rate

07Go · architecture

Arch-specific SIMD in Go

Go 1.27 introduces the archsimd package to provide low-level architecture-specific SIMD intrinsics for amd64, arm64, and wasm without requiring assembly. The API uses sensible naming conventions, zero-cost type reinterpretation, and opaque masks to improve usability and maintainability while achieving high performance. The resulting design enables developers to write optimized vectorized code safely with proper runtime CPU feature checking and compiler optimizations.

DEPTH ■■■■■12 min read3 weeks ago

Sign in to save and rate

08Cloudflare · performance

Yandex outage: Data shows that instead of going dark, malicious bots went on the move

Following physical strikes on Yandex data centers, overall HTTP traffic from the network dropped significantly, leading to speculation that malicious bot farms had been disabled. However, traffic analysis revealed that search crawling simply decreased while malicious automation quickly migrated to other hosting providers with identical fingerprints. Consequently, overall malicious bot traffic remained flat, demonstrating that network disruptions do not stop portable automated workloads.

DEPTH ■■■■■8 min read11 days ago

Incidents & Postmortems

Sign in to save and rate

09GitHub · architecture

Building Git infrastructure for agent-scale development

GitHub is redesigning its Git infrastructure to handle the massive surge in concurrent read and write operations driven by agentic software development and high-volume workloads. The team is decoupling storage from compute by leveraging Azure Blob Storage for durability and lightweight compute workers for requests, which separates scaling dimensions. In internal benchmarks, this approach achieves up to 35 times higher write throughput and independent read scalability.

DEPTH ■■■■■9 min read2 weeks ago

Infrastructure

Sign in to save and rate

10Cloudflare · postmortem

Inside Hyperdrive: How we solved a rare Hyperdrive MySQL caching bug

During the beta of MySQL support for Hyperdrive, engineers investigated rare empty query responses and connection hangs occurring in 0.001% of requests. They discovered that sharing the data center cache between client and endpoint nodes caused protocol capability mismatches when translating MySQL wire messages. The team resolved the issue by standardizing the cache to always store responses encoded with canonical Hyperdrive capabilities.

DEPTH ■■■■■9 min read11 days ago

MySQL

Sign in to save and rate

11GitHub · architecture

Staying Evergreen: How we automated secure access and repo hygiene in a shared org

Manual repository housekeeping and access reviews for outside collaborators become difficult to maintain as organizations scale. The team built Evergreen, a GitHub App that automates quarterly access reviews and stale repository archiving using native platform features and IssueOps. This automation successfully enforces secure defaults by revoking unanswered access while maintaining a full audit trail in git history.

DEPTH ■■■■■8 min read10 days ago

Sign in to save and rate

12Cloudflare · architecture

Under the hood, off the hot path: How D1 scales to millions of databases

Cloudflare scaled its serverless SQLite database, D1, to support millions of databases by decoupling the control plane from the data plane. The team used distributed metadata caching via Workers KV, optimized database connections through Hyperdrive, and implemented a self-correcting heartbeat mechanism. This architecture prevents centralized bottlenecks and allows D1 to handle rapid on-demand database creation efficiently.

DEPTH ■■■■■22 min read12 days ago

Databases

Sign in to save and rate

13Cloudflare · scaling

Rewinding the exponential: How we keep hardware usage down

Cloudflare tackled exponential traffic growth against linear hardware growth by continuously evolving their data pipeline architecture over five years. Key optimizations included breaking up monolithic schemas, switching to zstd compression, decoupling pipeline transit from database replication, decentralizing sampling, and moving aggregations earlier in the pipeline. These strategies significantly reduced backbone bandwidth usage, network congestion, and storage requirements while preserving data quality.

DEPTH ■■■■■12 min read12 days ago

Infrastructure

Sign in to save and rate

14GitHub · migration

Improving site performance by shipping more CSS

GitHub faced performance degradation on server-side rendering and initial page loads due to scaling issues with its CSS-in-JS solution. The engineering team executed a multi-year migration to CSS Modules and eliminated dynamic styling props using incremental rollouts, wrapper components, and automation tools. This resulted in significant performance gains, including 55% faster server-side rendering and the complete removal of styled-components.

DEPTH ■■■■■8 min read4 weeks ago

FrontendPerformance

Sign in to save and rate

15Cloudflare · architecture

Filter, reshape, and redact logs before export with Transformers

Cloudflare integrated SQL-based log transformation directly into its Logpush export pipeline, allowing customers to filter, redact, and reshape logs before delivery. The team chose to embed the Apache DataFusion engine in-process using Rust and Go across an Arrow IPC boundary to ensure high throughput and avoid network latency. As a result, the system processes high-volume log streams efficiently while maintaining predictable resource usage and strict delivery reliability.

DEPTH ■■■■■8 min read13 days ago

Sign in to save and rate

16GitHub · architecture

Rendering huge pull requests in the GitHub Copilot app

Rendering extremely large pull requests with millions of lines and hundreds of comments requires separating deterministic code row geometry from unpredictable dynamic comment blocks. The team implemented an idle-gated measurement scheduler, separate height indices, and identity-based scroll anchoring to maintain smooth scrolling. As a result, the pull request view remains performant and responsive even under extreme loads.

DEPTH ■■■■■14 min read4 weeks ago

Sign in to save and rate

17Cloudflare · architecture

Cloudflare deploys protections against php2shell vulnerability

Recent disclosures revealed critical remote code execution and data exposure vulnerabilities in the PHP runtime. To mitigate the threat before public disclosure, Cloudflare developed full transaction detection to combine request and response signals within the WAF. This capability enabled automatic deployment of rules protecting customers against the php2shell exploits.

DEPTH ■■■■■6 min read4 days ago

Security

Sign in to save and rate

18Cloudflare · architecture

How Commerce.com and Cloudflare are getting storefronts ready for AI agents

Commerce.com and Cloudflare collaborated to enable WebMCP at the edge for nearly 100,000 storefronts, allowing AI agents to interact reliably with e-commerce sites using structured tools rather than fragile HTML scraping. The team implemented edge-level configuration rules using custom hostname metadata to provide individual merchants with a seamless opt-out mechanism and added support for custom MCP paths. This integration allows agents to execute shopping tasks directly within the active browser session while ensuring fallback safety and zero extra latency for opted-out stores.

DEPTH ■■■■■6 min read4 days ago

Machine Learning

Sign in to save and rate

19Stripe · practice

Why I tried to kill token billing (and why we kept it)

The author examines the limitations of token-based billing as a customer-facing pricing model, noting that it exposes internal margins and commoditizes AI products. The company explored abandoning token billing entirely but realized its necessity for backend cost tracking and margin management. Ultimately, the piece proposes unified credits and output-based pricing as better ways to align invoices with customer value.

DEPTH ■■■■■7 min read3 weeks ago

Sign in to save and rate

20Cloudflare · postmortem

8 eMudhra certificates are compromised. Here's what you need to know

Private keys associated with eight eMudhra intermediate certificates were compromised, allowing potential traffic interception. Cloudflare prioritized patching critical services, released client and tunnel updates, and deployed mitigations across its products. Customers are advised to upgrade affected software, update custom trust stores, and avoid disabling verification despite error messages.

DEPTH ■■■■■4 min read4 days ago

Security

Sign in to save and rate