Uh, how often are you using the Internet to connect to a computer in your home town? Maybe 5% of the time?
I’ve never used Starlink, but with a basic understanding of geography and optics, I’m going to bet that in most scenarios the latency difference between Starlink and fiber is negligible, sometimes even being faster on Starlink, depending on the situation.
That said, I’m not suggesting Starlink is a realistic replacement for fiber, just that latency isn’t the big issue. (It has other serious issues)
Ok, so actual question, How useful are CDN endpoints these days with https everywhere? Because most encrypted content is unique to a single web user, caching isn’t super useful. Also you can’t cache live content like video calls or online games. I’d imagine the percentage of cacheable content is actually fairly low these days. But like I said, I don’t actually know the answer to this, i’d be curious to hear your take.
Edit: it’s weird to get down votes for a question.
HTTPS / TLS has little to do with it. Don’t think of the endpoint as a cache between you and the origin. The DNS name given to the endpoint is the origin from your browser’s perspective. How content gets cached on the backend is irrelevant to the browser.
Live video that someone else in your area is also watching is cacheable. Images to load a page, very cacheable. The personal stuff is mostly HTML specific to you but that’s quite small.
Uh, how often are you using the Internet to connect to a computer in your home town? Maybe 5% of the time?
I’ve never used Starlink, but with a basic understanding of geography and optics, I’m going to bet that in most scenarios the latency difference between Starlink and fiber is negligible, sometimes even being faster on Starlink, depending on the situation.
That said, I’m not suggesting Starlink is a realistic replacement for fiber, just that latency isn’t the big issue. (It has other serious issues)
Much more frequently than you think with CDN endpoints.
Ok, so actual question, How useful are CDN endpoints these days with https everywhere? Because most encrypted content is unique to a single web user, caching isn’t super useful. Also you can’t cache live content like video calls or online games. I’d imagine the percentage of cacheable content is actually fairly low these days. But like I said, I don’t actually know the answer to this, i’d be curious to hear your take.
Edit: it’s weird to get down votes for a question.
HTTPS / TLS has little to do with it. Don’t think of the endpoint as a cache between you and the origin. The DNS name given to the endpoint is the origin from your browser’s perspective. How content gets cached on the backend is irrelevant to the browser. Live video that someone else in your area is also watching is cacheable. Images to load a page, very cacheable. The personal stuff is mostly HTML specific to you but that’s quite small.
HTTPS can in fact be cached, and most modern browsers will do so unless given a header or something to tell it not to.
Source: Devtools network tab + https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Caching