Netflix · 2026
Ontology-Driven Observability: Building an End-to-End Knowledge Graph at Netflix Scale
Netflix found a typical regression investigation took about four hours, mostly spent reconstructing relationships between systems like Atlas, Radar, Spinnaker, PagerDuty, incident.io and Slack that each named the same thing differently. It built an Observability Ontology on the W3C stack (RDF, OWL, SHACL, SPARQL), stored as a knowledge graph in QuipuDB, its homegrown distributed quad store built on the Rust key-value store redb. Enrichers, some LLM-based, turn noisy inputs into typed triples, every application is validated against a catalog of about 49,000 entries, and dependency edges are capped. A correlation engine scores chains across 13 signal types within a ten-minute window, discarding anything under 0.6 confidence, and an agentic AutoRCA system reads the graph to hand engineers ranked, evidence-backed hypotheses.
~65M concurrent streams (Paul vs. Tyson, Nov 2024)2B+ requests/dayknowledge graphsobservabilityroot cause analysisRDFOWLSHACL
Meta · 2026
F3 Lightning: How Meta Accelerates Ads ML Features to Production at Scale
Meta's Facebook Feature Framework (F3) compiles ads ranking features into one merged DAG so shared work runs once, but that graph was also the release unit, so one bad definition blocked every other feature as the catalog grew past 20,000 features per request. F3 Lightning makes each feature an independently compiled, validated, deployed, and rolled-back configuration, then rebuilds shared execution at service startup: stable identifiers derived from each computation's meaning, one flattened execution plan that deduplicates common nodes, a single per-request memory buffer, and dense integer slot mapping so request-path reads are direct array indexes. Comparable extraction features now reach production about 3.6x faster than traditional F3 with no increase in infrastructure compute cost.
20,000+ features per ads ranking request~3.6x faster feature releases to productionper-feature releaseshared execution planstable computation identifiersF3DAG feature graphsAds ML
Meta · 2026
Inside Prometheus: Meta's Journey to a Gigawatt-Scale Supercluster
Meta turned its New Albany, Ohio data center site from web traffic into Prometheus, a gigawatt-scale AI supercluster spanning multiple interconnected buildings that behaves as one machine. It runs NVL72 racks (Catalina on GB200 with 800G of scale-out per GPU, Clemente on GB300 in a single rack) on a dedicated Ethernet back-end network for GPU-to-GPU traffic. Reliability work pushed pre-training goodput above 85% and mean time between interruptions past 54K GPU hours, and the cluster is growing toward roughly 1 million GPUs.
gigawatt-scale superclusterhundreds of thousands of GPUs today, ~1 million plannedGPU clustersdistributed traininghardware reliabilityNVIDIA GB200 NVL72NVIDIA GB300 NVL72Ethernet back-end network