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?
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. The first time a user requests a piece of content, the CDN pulls it from the origin server, caches it on the edge server, and serves it.
.....
.....
.....
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
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.
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.