Avoid stacking everything on a single vendor when it really matters (DNS + CDN + WAF + hosting all in one basket).
I'm not sure I understand several of the statements in this article, such as the above. If my entire service is built on Cloudflare (Workers, DNS, CDN, WAF), moving my DNS to GoDaddy doesn't improve my site's reliability. The only way I'd improve reliability is by having full redundancy of each component, end to end. In other words, a region or availability zone.
There's an industry gap for good alternatives to Cloudflare, but they already make so little money for the value they're providing, why bother?
I think you mean: If your entire customer-facing service is built on Cloudflare and the rest doesn't matter, etc.
But I suspect that the rest matters. For example, will you benefit from having your domain working when the admin team works on an outage? Yes/maybe/no? My answer is the middle one.
As a matter of fact, unless you’re increasing redundancy, stacking multiple different vendors on top of each other will only increase the chances of things going down.
Avoid stacking everything on a single vendor when it really matters (DNS + CDN + WAF + hosting all in one basket).
I'm not sure I understand several of the statements in this article, such as the above. If my entire service is built on Cloudflare (Workers, DNS, CDN, WAF), moving my DNS to GoDaddy doesn't improve my site's reliability. The only way I'd improve reliability is by having full redundancy of each component, end to end. In other words, a region or availability zone.
There's an industry gap for good alternatives to Cloudflare, but they already make so little money for the value they're providing, why bother?