from Hacker News

Cloudflare’s Zero Egress Fee Object Storage, R2, Is Now GA

by elithrar on 9/21/22, 1:06 PM with 33 comments

• by catapart on 9/21/22, 2:47 PM

  One thing I really like about CloudFlare is that they seem to have people who can correctly identify friction-points for developers and have a solid plan on how to solve them. Looking forward to messing with this!

• by TimCTRL on 9/21/22, 3:00 PM

  I wish we had the same pricing model for Cloudflare Images. I have never understood the CF Images pricing model [1]

  1. https://www.cloudflare.com/en-gb/products/cloudflare-images/....

• by fabian2k on 9/21/22, 2:40 PM

  I find it much easier to reason about pure storage-based pricing compared to storage and egress-based pricing. I can much easier limit how much people can store in my application than add something much harder to understand like transfer quotas. So independent of how R2 compares purely on price I think having a big entry with a much simpler pricing scheme is a win already.

• by dafelst on 9/21/22, 3:02 PM

  While conceptually I love the idea of not having to explicitly set the region of an object I'm storing, I feel like (especially in a distributed team or product) this could end up with a mishmash of data distributed all over the place with a bunch of different and unpredictable access time and latency characteristics.

  Maybe the solution here is "just make sure the asset is cached on the edge" but for first access there has still got to be some impact no?

  I'd love to see some test/benchmarks on access latency for stuff uploaded by say a colleague or app hosted in the EU or Asia with me in the US.

• by adoxyz on 9/21/22, 5:19 PM

  Loving R2. I am having an issue of uploading larger files though, like 100MB+. The error I get is:

  Unable to write file at location: JrF3FnkA9W.webm. An exception occurred while uploading parts to a multipart upload. The following parts had errors: - Part 17: Error executing "UploadPart" on {URL}

  with the message:

  "Reduce your concurrent request rate for the same object."

  Is this an issue on my end or CloudFlare's? I'm not doing anything aggressive, trying to upload 1 video at a time using Laravel's S3 filesystem driver. It works great on smaller files.

• by CodesInChaos on 9/21/22, 4:27 PM

  Using the same price for read requests, regardless of size feels weird to me (S3 is the same for internal use). The cost to the provider of serving a 100kB file and a 100GB file must be quite different, so why price them the same to the user?

• by waskip on 9/21/22, 2:33 PM

  I’m storing 87TB on https://wasabi.com/ for ~$515 a month

• by jve on 9/21/22, 2:39 PM

  Oh, wow, upvotes keep coming in, but fell of of front page really fast. Fell out of HN algorithm grace really fast.

• by TheP1000 on 9/21/22, 4:15 PM

  The automatic region thing is problematic for many companies.

  I would much rather be able to explicitly choose this and know that customers data is where I told them it would be.

• by archon810 on 9/28/22, 4:53 AM

  Does anyone from the R2 team happen to know if there's a roadmap ETA on this one yet?

  https://community.cloudflare.com/t/r2-per-bucket-token/41105...

  The fact that you can't separate data for prod and dev with a product that's in GA now is kind of nuts.

• by banana_giraffe on 9/22/22, 8:49 PM

  I really want to use this, but sadly the one thing that's missing is any sort of bucket access logging.

  Unless I'm missing something with how this fits in with Cloudflare's other services.

• by underbluewaters on 9/21/22, 2:44 PM

  I'm excited to see more details on how R2 data is going to be replicated across different data centers in the future. I had assumed this was already operational based on previous blog posts so I'm a little disappointed to learn that is still TBD. It's a major reason I chose R2 over S3 as I don't want to manage moving around data for different tenants myself.

• by maxgashkov on 10/1/22, 8:06 AM

  Still no word on durability guarantees even for GA?