/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

Databases Frontend Infrastructure MySQL Clear all

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
Databases Performance Redis
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
03Meta · architecture
Inside Prometheus: Meta’s Journey to a Gigawatt-Scale Supercluster
Meta built Prometheus, a gigawatt-scale AI supercluster designed to scale up to one million GPUs using multi-generation NVIDIA hardware and specialized backend Ethernet networks. The team achieved high goodput and significantly reduced system interruptions by implementing an in-rack sparing strategy, parallelism-aware fault tolerance, and close co-engineering with vendors. These infrastructure advancements allowed the team to successfully train frontier foundational models like Muse Wonder.
DEPTH ■■■■■17 min read6 days ago
Infrastructure Machine Learning
Sign in to save and rate
04Meta · practice
How Meta Built Forum With AI-Native Engineering
Meta engineers built the Forum app using a human-on-the-loop AI agent workflow that automated planning, building, testing, and verification. By shifting focus from code generation to automated verification, tooling improvements, and architectural legibility, the team reached feature parity in eight weeks while catching systemic memory issues early.
DEPTH ■■■■■8 min read10 days ago
Frontend Mobile
Sign in to save and rate
05Cloudflare · 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
06Cloudflare · 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
07GitHub · 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
08Dropbox · architecture
Evolving our calendar assistant Reclaim to be AI-native without starting over
Dropbox engineers evolved their calendar assistant, Reclaim, to support natural-language AI requests by building a custom agent platform that integrates with existing scheduling logic. They utilized a shared action system and a Preview Mode backed by Redis to ensure AI suggestions are consistent and reviewable before affecting real calendars. This approach allows the product to adopt AI capabilities without fragmenting its core architecture or duplicating functionality.
DEPTH ■■■■■7 min read3 weeks ago
Infrastructure Machine Learning
Sign in to save and rate
09Cloudflare · 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
10Meta · scaling
2026 World Cup: Breaking Records, Spiky Charts and Reliability at Scale
Meta's infrastructure handled record-breaking traffic during the 2026 World Cup, including 30 million messages per second on WhatsApp, by relying on automated load balancing, capacity buffers, and targeted pre-builds. Traffic patterns revealed that surges occurred primarily during breaks rather than gameplay, requiring region-specific forecasting rather than cross-region load shifting. The systems maintained full reliability and allowed normal continuous deployment schedules to continue without manual intervention or system freezes.
DEPTH ■■■■■5 min read10 days ago
Infrastructure
Sign in to save and rate
11Heroku · architecture
Front-End Web Deep Dive: Runtime Config
Front-end web applications traditionally bake environment variables into build artifacts, requiring a full rebuild to change configurations across environments. To solve this, a new approach injects runtime environment variables directly into the HTML document's head element as data attributes via a Cloud Native Buildpack. This enables zero-rebuild configuration changes while remaining compatible with browser security standards like CSP.
DEPTH ■■■■■3 min read10 days ago
Frontend
Sign in to save and rate
12GitHub · 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
Frontend Performance
Sign in to save and rate
13Meta · migration
Shipping Media Over QUIC at Meta Scale for Instagram Live Ingest
Meta deployed the emerging Media over QUIC (MoQ) protocol for Instagram Live ingest on iOS and Android to replace their legacy RUSH protocol. By using edge translation to avoid backend rewrites and a phased rollout strategy, the team achieved metric parity with the old protocol without regressions. This deployment establishes a foundation to extend MoQ across Meta's applications for lower-latency and more resilient video streaming.
DEPTH ■■■■■8 min read13 days ago
Frontend Mobile
Sign in to save and rate
14PlanetScale · scaling
Handling hot shards
Growing applications often encounter hot shards when certain tenants or data subsets outgrow initial sharding strategies based on workspace IDs. To mitigate this, teams can scale up resources, isolate large tenants into specific key ranges, or fundamentally change the shard key for problematic tables based on access patterns. Neki facilitates these adjustments by allowing declarative data topologies and online resharding without downtime.
DEPTH ■■■■■7 min read3 weeks ago
MySQL PostgreSQL
Sign in to save and rate
15Grab · architecture
Data Mesh at Grab (Part III): Operationalizing data reliability with automated DPIs
Grab addressed runtime data reliability issues in its data mesh by implementing automated Data Production Issues (DPIs). The system uses an incident orchestrator to detect contract breaches, a Data Health API for cross-platform root cause analysis, and Hugo for automated remediation. This approach resolved 86.9 percent of incidents automatically and made mean time to resolve six times faster.
DEPTH ■■■■■12 min read8 weeks ago
Databases Observability
Sign in to save and rate