What is the difference between a Push CDN and a Pull CDN?
A Pull CDN fetches assets on demand from the origin upon the first cache miss and caches them according to HTTP headers. A Push CDN requires the application or CI pipeline to proactively upload content to edge storage prior to user requests.
Answered in
Content Delivery Networks Demystified: Edge Caching, Origin Offload and Traffic ShapingHow CDNs route requests to distributed edge locations, cache reusable responses, reduce origin load, and manage freshness without overclaiming latency gains.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the core distinction between database replication and database sharding?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.