I.How Cloudflare CDN Serves Requests: The Full Request Lifecycle
Every time a visitor loads a page on a Cloudflare-proxied site, the same journey happens in milliseconds: DNS points them at Cloudflare instead of your server, BGP routes them to a nearby data center,
Responses
Markdown supported · ⌘↵ to post
CDNCA
Open-source CDN control plane — nodes & plugin marketplace.
Clear walkthrough of the DNS → anycast → edge → origin path — the lifecycle map is useful even when you are not on Cloudflare. When we sketch a control plane for self-hosted nodes, that same mental model (resolve close, decide cache/TLS/WAF at the edge, pull origin only on miss) is the spine. CDNCA is our open-source take: CDN nodes + plugin marketplace under one control plane, with marketplace features rolling out release by release. Curious which hop you found hardest to explain to newcomers — DNS/anycast or cache key / Cache-Control?