@Ashish :I think the cache miss arrow is incorrect ? In a “pure” CDN flow, the end user never goes directly to the origin when there’s a cache miss. Instead, the user’s request still goes to the CDN edge server, and the CDN edge server then forwards that request (a “miss”) upstream to the origin. So strictly speaking, the arrow labeled “Cache Miss” should come from the CDN edge server to the origin server, not from the user to the origin server.
@Ashish :I think the cache miss arrow is incorrect ? In a “pure” CDN flow, the end user never goes directly to the origin when there’s a cache miss. Instead, the user’s request still goes to the CDN edge server, and the CDN edge server then forwards that request (a “miss”) upstream to the origin. So strictly speaking, the arrow labeled “Cache Miss” should come from the CDN edge server to the origin server, not from the user to the origin server.
Thank you for sharing. Worth reading😄
DNS, CDN & DDoS — Key Points
DNS = resolves domain → IP, uses Anycast + caching to handle DNS DDoS.
CDN = delivers content via edge servers, reduces latency + bandwidth cost.
Anycast = same IP globally, routes users/attacks to nearest POP.
DDoS Mitigation:
DNS layer → absorbs query floods with global Anycast & redundancy.
CDN layer → absorbs HTTP floods, filters bad traffic, caches static content, hides origin.
Cost Impact:
Without protection → huge infra + bandwidth bills + downtime.
With CDN/DNS → predictable subscription cost, origin shielded.
Thanks
Thanks For sharing this lesson.