Skip to content
Discussion options

You must be logged in to vote

@ShlokDesai33 No worries at all 😊

Let me walk you through this: A CDN is essentially a cache located in front of your application, which is often distributed worldwide. When a user requests a route, the request will be send to the CDN first. If the CDN can handle the request, it immediately sends back the response, ensuring that the request does not reach your application. In cases where the CDN does not have a copy of the response data, it reaches out to your application. The CDN then caches the response and sends it back to the user.

Ryan Florence has an excellent talk on this topic CDN Caching, Static Site Generation, and Server Side Rendering
and another one on HTTP Caching in general

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@ShlokDesai33
Comment options

@akoenig
Comment options

Answer selected by ShlokDesai33
@ShlokDesai33
Comment options

@ShlokDesai33
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants