3 ms·
And to be fair it's not a bad point. AWS and CloudFront is not without it's problems, but every time I've tried to build anything non-trivial with Cloudflare's
by eins1234 5y ago
And to be fair it's not a bad point. AWS and CloudFront is not without it's problems, but every time I've tried to build anything non-trivial with Cloudflare's CDN I've found that some table-stakes feature turns out to be locked behind a $5000+ enterprise plan, with no option to pay a more reasonable price for just the feature itself and associated usage.
I've come to the conclusion that Cloudflare's CDN is only really worthwhile if I'm building something tiny and basic that will never conceivably need any of their enterprise features (and I've turned out to be wrong about this down the line on many occasions, so YMMV), or something super ambitious where I'm willing and able to go all in on the enterprise plan and hope that eventually economies of scale on egress costs will kick in and turn it into a good deal. That leaves a giant gaping hole in the middle where it makes more sense to go with a different CDN like Cloudfront or Fastly where the bandwidth isn't free, but advanced features are included or charged on a usage basis (these days most of my projects fall into this category).