Live data from Hacker News

Will Cloudflare R2 Win Customers from Amazon S3?

taloflow.ai

211–213 of 213 posts

Re: Will Cloudflare R2 Win Customers from Amazon S3?

#211

Earlier quoted context omitted.

That's not for data you Will actually use. You are only including one of the many cysts ( egress and retrieval) + it's really slow. Cloudflare brings R2 to the edge.

Integration is an interesting problem though. With Scaleway's c14 cold storage, I felt the reasonable choices were use their S3 services for more or don't use their S3 oriented archive service at all. Moving everything around to different S3 services for different purposes seems like something I don't want to sign up for.

But it is interesting if you want to use different services of different clouds to pick the best ones for their use-case.

Egress is the cost that prevents that.

Re: Will Cloudflare R2 Win Customers from Amazon S3?

#212
post #92
post #87

What I want to see is Cloudflare enable hosting static websites on R2. For me that would be an absolute game changer. I know you can already host websites on Cloudflare using another service but I want to see R2 get enabled.

We've heard this a few times and will support it :). Also, shameless plug for Cloudflare Pages to host on CF today.

I recently deployed a small, static site using a Cloudflare Worker Site, using the Wrangler CLI tool to publish it - I'd never used Cloudflare Workers before, but it was easy, and whole dev UX from start to finish was superb!

I looked into Cloudflare Pages first, which on the face of it would be a better fit - but AFAICS it can only deploy from code hosted in a GitHub repo. Not even git in general, but specifically only with GitHub - and I'm using Azure DevOps.

I'd love to see additional deployment mechanisms for Pages - ideally support would be added to Wrangler, so I could deploy from a CD pipeline hosted anywhere, just like I can for Workers.

Re: Will Cloudflare R2 Win Customers from Amazon S3?

#213
post #199

Earlier quoted context omitted.

Echoing this. We've just made use of that very offer to shift >2billion objects (120TB) from S3 to B2. Migration took over a month but we weren't billed for any of it and are very happy so far.

Just curious, were you optimising for storage or serving costs, and were the expected savings realized? I've been itching to try live serving out of B2, but its latency jumps around quite a lot, and the hot cache layer does not stream large (>100MB) objects during first fetch, so it's not without some downsides.

The objects we moved to B2 are essentially archive material and not expected to be regularly accessed, so it was purely a cost optimisation. We'll be adding another ~50TB per year to B2 so we expect the long term savings to be significant versus leaving these objects in S3. Because of the object count (and per object size), moving them to Glacier was not an option.
Post reply on HN