Hacker News new | ask | show | jobs
by jsheard 208 days ago
They don't name names but it's probably due to the ongoing Cloudflare explosion. I know the DigitalOcean Spaces CDN is just Cloudflare under the hood.
1 comments

Just spaces CDN, not spaces - you'd think they'd just turn the CDN off for a bit.
You can't just "turn off CDN" on the modern internet. You'd instantly DDOS your customers' origins. They're not provisioned to handle it, and even if they were the size of the pipe going to them isn't. The modern internet is built around the expectation that everything is distributed via CDN. Some more "traditional" websites would probably be fine.
Might be just me, but I can think of many origins under my control which could live without a (non-functional) CDN for a while.

CDN is great for peak-load, latency reductions, and cost - but not all sites depend on it for scale 24/7

If you are DO you could, you just decided not to bother. They control the origins it's spaces (s3), so they could absolutely spin up further gateways or a cache layer and then turn the CDN off.
Either you are wrong and they do not have the capacity to do that, or they have decided it is acceptable to be down because a major provider is down

I imagine a cache layer cannot be that easy to spin up - otherwise why would they outsource it?

You outsource it because clouflare have more locations than you so offer lower latency and can offer it at a cost that's cheaper or the same price as doing it yourself.
Which suggests its expensive enough for it to be unlikely they just have the capacity lying around to spin up.
nit: that's more DoS (from a handful of DO LBs) than DDoS.