0% completed
Push CDN vs. Pull CDN
Content has to reach the edge servers somehow. There are two ways, and they differ on one question: who moves the content, and when?
Two terms first. The origin server is the machine that holds the master copy of the content. The content provider is whoever owns that content and runs the origin, which in these designs means you.
In a Pull CDN, the CDN fetches content from the origin when a user first asks for it. In a Push CDN, the content provider uploads content to the CDN ahead of time.
Pull CDN
By default the CDN stores nothing
.....
.....
.....
Ron P
· a month ago
What is content provider in the case of Push CDN? Is it origin server? If not then where is the origin server in picture in this scheme? Pls clarify
nair mohan
· a year ago
This disadvantage seems incorrect. All cached content will obviously be stored on origin servers as well no matter which approach is taken
Aldo Gutiérrez Alcalá
· 3 years ago
How would you avoid the single point of failure on the origin and CDN server? I can imagine serving a load balancer kind of.
Anand Mohan
· 3 years ago
Please explain the above statement. It sounds bit counterintuitive.
In this case Pull CDN seems like a better choice as in Push CDN the resources would be cached but not accessed frequently leading to un-optimal utilisation of storage resource.
Reading Progress
0%