← Wednesday, October 14, 2026ArchitectureCase study
Cloudflare’s data pipeline delivers two billion events per second with less hardware
Cloudflare describes schema changes, compression adjustments, and replication redesigns to keep hardware growth below data-volume growth; the work deferred an equivalent of two and a half years of hardware expansion. The techniques offer lessons for teams operating high-volume distributed data pipelines.
- What
- Cloudflare’s data pipeline handles roughly two billion events per second from its globally distributed network.
- How
- Logfwdr forwards events to centralized receivers, which enqueue them in Buftee; consumers fetch them and send them to destinations such as ClickHouse.
- Why it matters
- Schema changes, compression, replication, decentralized sampling and in-pipeline aggregation have helped offset traffic growth relative to hardware.
Discussion
Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.
Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.
