3 ms·
> All content delivery networks do not host content (arguable) but only effectively _relay_ content such that delivery is faster. Once the origin server goes do
by stephengillie 11y ago
> All content delivery networks do not host content (arguable) but only effectively _relay_ content such that delivery is faster. Once the origin server goes down, so does the content. This is an integral part of how CDNs operate.
What's the point of a service that caches and accelerates errors?
If this is by design, then I don't understand most of the value proposition of CDNs. If my origin is overloaded, down, or throwing intermittent errors, I want the CDN to cover for this. But no, a CDN is just a set of mirrors for whatever you're serving now.
- slimsag 11y ago> If my origin is overloaded, down, or throwing intermittent errors, I want the CDN to cover for this. Sure, that is another configuration available by many CDNs as well. Many CDNs however suggest that your origin is contacted by nobody except the CDN itself (not true for CloudFlare, though). It can then perfectly replicate your origin's content as it is updated without overbearing your origin.
- tomkwok 11y ago> Many CDNs however suggest that your origin is contacted by nobody except the CDN itself (not true for CloudFlare, though). CloudFlare does as well. See https://blog.cloudflare.com/ddos-prevention-protecting-the-origin/ https://blog.cloudflare.com/ddos-prevention-protecting-the-o...
- grrowl 11y agoOnly within the scope of DDoS protection. There's no use relying on Cloudflare to keep your site up in that scenario while publicly broadcasting your real server IP, ripe and defenceless, at direct.mydomain.com