News for hackers. Stuff that matters.
Re:Cloudflare S-1 by the_duke on Thursday August 15, 2019 @01:14PM (#20707287)
My guess: new development-intensive products like the 1.1.1 DNS, Wireguard, WAF etc plus general scaling and growth on one side, and increased competition from established cloud services on the other.

After all, if you are already on eg AWS, just using Cloudfront is temptingly easy. (even if bad from a redundancy perspective)

Re:Cloudflare S-1 by qes on Thursday August 15, 2019 @02:53PM (#20708415)
It's easy, but we're saving thousands of dollars a month using Cloudflare instead of our cloud service provider's CDN (~250TB/month), and that's without any kind of discounted egress agreement between our cloud service and Cloudflare (which is supposed to be in the works, but it's been literally years with no further word)
Re:Cloudflare S-1 by jve on Friday August 16, 2019 @04:42AM (#20713269)
You missed Magic Transit that was announced few days ago: https://blog.cloudflare.com/magic-transit/
Re:Cloudflare S-1 by judge2020 on Thursday August 15, 2019 @02:08PM (#20707946)
AWS also offers a managed WAF - https://aws.amazon.com/waf/
Re:Cloudflare S-1 by zymhan on Thursday August 15, 2019 @03:25PM (#20708743)
> just using Cloudfront is temptingly easy

IMO this is giving way too much credit to AWS

Re:Cloudflare S-1 by stingraycharles on Thursday August 15, 2019 @03:41PM (#20708886)
Assuming you’re already integrated on AWS, just using Cloudfront is a lot easier than Cloudflare. You’re likely already using S3, maybe use CloudFormation as well. Then it’s often much more straightforward to use AWS services rather than a third party provider.