A cdn is largely a value prop to reduce latency for static web pages, so that someone coming from a link get a page load asap. Once you have a dynamic or hybrid app, the value diminishes rather quickly, I assume. Potentially it could become negative if you have different points of failures and cache inconsistencies.
Unless CloudFlare cables are somehow shinier than the rest of the internet’s, adding one hop almost certainly adds latency. More hops more time.
In some instances where the original server was closer than CF’s edge, I measured increased time even for cached content, effectively making CF slower for every request by that specific user.
> Unless CloudFlare cables are somehow shinier than the rest of the internet’s
Unrelated, but these mega actors sometimes have such shiny cables, because they can route on their internal network across the globe. Iirc Cloudflare does that for some/all traffic(?). But you’re right, all else equal more hops = worse, and I’d be unsurprised if Cloudflare overstates the benefits of using them.
> Unless CloudFlare cables are somehow shinier than the rest of the internet’s, adding one hop almost certainly adds latency. More hops more time.
In my experience, CloudFlare (and other CDNs) can often provide a better route then a regular ISP. Sometimes downloading speed is really slow, switching to CloudFlare wrap (VPN) can at least double or triple the speed.
I assume that’s because a VPN doesn’t let the ISP do any traffic shaping, which isn’t the case for regular CDNs (unless the ISP itself “positively traffic shapes” for)
Warp also regularly lets me escape public Wi-Fi’s where in-browser uploads fail.
You're not factoring in the DDoS protection, that's why the answer you got is so clear. It _may_ still be value negative, but it probably depends on the tradeoffs one cares about.
