3 ms·

All you can edge cache, though, is static content. That's generally true. This was one of the problems I worked on at NuevoCloud.. for dynamic pages, it would

All you can edge cache, though, is static content. That's generally true. This was one of the problems I worked on at NuevoCloud.. for dynamic pages, it would look at the page, and determine which sections of the page are static or dynamic/unique. A PoP near the server would do the analysis, and then send the unique sections to the edge PoP (near the visitor) for it to be reassembled. So the static portions of a page would be cached, and you would only be sending the unique parts of a page over long distances... and that would also be compressed, encrypted, and sent over an optimized connection (ie: no handshake delay, etc). Of course, the difference is more significant the further away you are from the origin. I don't know of any other CDNs doing that.. but I imagine they'll eventually get to it. So I would look for that in the future, even if you don't use our CDN.

Tushon 10y ago
That sounds like Raygun from Cloudflare and ESI (potentially) from Fastly. https://www.cloudflare.com/docs/railgun/intro.html https://www.cloudflare.com/docs/railgun/intro.html https://www.fastly.com/blog/using-esi-part-1-simple-edge-side-include https://www.fastly.com/blog/using-esi-part-1-simple-edge-sid...
- rgbrenner 10y ago
  ESI isn't from fastly.. it's an old W3C standard from 15 years ago. You have to markup all of your HTML to use it though. So Cloudflare made a nice improvement with Railgun, so that you don't need to markup your HTML.. but you have to setup and run railgun on your server, so it can compare the pages. (I don't think it does anything else other than basically diving up the page content so individual parts can be cached.. but someone from cloudflare is welcome to tell me I'm wrong.) To compare our tech to railgun: - there's nothing to setup or run (you just enable it for the zone), and you don't need to modify your pages (like you do for esi) - it works on all content, including binaries/images/etc - each page/file only needs to be analyzed once. So if a page is first seen in a request from Japan, a 2nd request from Germany would be accelerated, even though that PoP has never seen the page before. - Because of the way it works, it's paired with adaptive routing, which routes the data over the fastest active link between the pops.. so there's no handshake setup time, ssl negotiation time, etc over the long haul. When its enabled, we actually use it to transmit most content between the pops.. so it also accelerates revalidation of static content, etc. Edit: also it's not $200/mo.. it's just included with your account.

Tushon 10y ago

That sounds like Raygun from Cloudflare and ESI (potentially) from Fastly. https://www.cloudflare.com/docs/railgun/intro.html https://www.cloudflare.com/docs/railgun/intro.html https://www.fastly.com/blog/using-esi-part-1-simple-edge-side-include https://www.fastly.com/blog/using-esi-part-1-simple-edge-sid...

rgbrenner 10y ago
ESI isn't from fastly.. it's an old W3C standard from 15 years ago. You have to markup all of your HTML to use it though. So Cloudflare made a nice improvement with Railgun, so that you don't need to markup your HTML.. but you have to setup and run railgun on your server, so it can compare the pages. (I don't think it does anything else other than basically diving up the page content so individual parts can be cached.. but someone from cloudflare is welcome to tell me I'm wrong.) To compare our tech to railgun: - there's nothing to setup or run (you just enable it for the zone), and you don't need to modify your pages (like you do for esi) - it works on all content, including binaries/images/etc - each page/file only needs to be analyzed once. So if a page is first seen in a request from Japan, a 2nd request from Germany would be accelerated, even though that PoP has never seen the page before. - Because of the way it works, it's paired with adaptive routing, which routes the data over the fastest active link between the pops.. so there's no handshake setup time, ssl negotiation time, etc over the long haul. When its enabled, we actually use it to transmit most content between the pops.. so it also accelerates revalidation of static content, etc. Edit: also it's not $200/mo.. it's just included with your account.