4 ms·
I think the solution here isn’t “don’t use Cloudflare” … IMO if you need high availability and can’t tolerate downtime, then deploy and split load between 2 or
by cj 3y ago
I think the solution here isn’t “don’t use Cloudflare” … IMO if you need high availability and can’t tolerate downtime, then deploy and split load between 2 or more providers (e.g. Cloudflare, Fastly) and 2 or more clouds.
The centralization around AWS and GCP and Azure is more concerning to me than the centralization around Cloudflare. It’s not obvious to me why lots of people using Cloudflare is any worse than lots of people using AWS.
If we go even deeper, the entire internet runs on a limited number of undersea cables connecting continents. That in particular has always seemed like the most vulnerable aspect of the internet, considering a targeted attack on < 100 locations could meaningfully cut off internet access for millions (billions?) of people for an extended period of time.
- jabart 3y agoThis. If downtime is that big of an issue, you should be on Cloudflare's business/enterprise plan which allows CNAME DNS, have redundant DNS providers with 30s TTLs that flip over to another provider. Better yet if you can 50/50 the traffic and 100/0 it when something goes bad. Downside is cost and DNSSEC has an issue with multiple keys. I think there was an RFC on that though I'm not sure it's well supported yet.
- pixl97 3y ago>then deploy and split load between 2 or more providers (e.g. Cloudflare, Fastly) How does this work when most edge providers manage your DNS to point at the available servers they have? Also, if you "HAVE" to be online, then you're the type of target that's at big risk of DDOS which complicates this even further.
- wbl 3y agoUsually each one will give you a CBAME, your DNS or Cedexic decides, sometimes per client. It's a pretty common setup although can complicate config changes and taking advantage of new features.