2 ms·

1. TFA goes R2 clients will be able to enable caching (in the near future). A couple questions: 1a. Cloudflare Cache is free for users (up to 500MB per file fo

1. TFA goes R2 clients will be able to enable caching (in the near future). A couple questions: 1a. Cloudflare Cache is free for users (up to 500MB per file for unlimited files), but if R2 uses it transparently, are reads from cache metered per R2 pricing? And what about the file-size limits that apply to free/pro accounts? 1b. How is strong-consistency guaranteed despite caches in front of the bucket? I guess cache-invalidation can be done through Durable Object (DO) Alarms or some such? Or, would this guarantee no longer hold? 2. TFA mentions in the passing that R2 utilizes DO (for presumably metadata / journal?). Cloudflare once wrote in detail about how DO is used in a pretty novel way to power wrangler tail, and so I was wondering if there's something novel about R2's use of DO, too? 3. In-Worker API: Are customers metered for both In-Worker API (duration and invocation) and R2 (Class A / Class B)? If so, that makes Class B operations almost twice as expensive than S3 (excluding egress). 4. Any ETA on "Public buckets"? 5. Has Cloudflare rolled out newer server designs just for R2 (aka Dropbox's MagicPocket)? 6. Is serving media content (say, audio and video) an acceptable use-case for R2? 7. Any plans for Kinesis Firehose (a managed-ingestion pipeline) esque product to front R2? Thanks.

vlovich123 5y ago
1a. I don't think we have anything to share with regards to the logistics of putting cache in front of R2 or how that product will work. 1b. Unavoidably as you guess you'd be giving up the consistency. Presumably the consistency guarantees would be part of the cache-control header you associate with the object. Cache purging would probably work similar & we have exciting upcoming news about major performance improvements for that. But again, since we don't have any idea of what that product looks like, hard to say. 2. There is. I have a bunch of technical blog posts written but we decided to punt on providing that detail for a few months just to give everyone some breathing room. R2 does have one important extension we got the DO team to build just for us (not 1 instance of the code instantiated). That piece will only be available for R2. R2 is also driving performance improvements & API improvements to DO that will almost certainly percolate out to external users. 3. The equivalent model would be AWS Lambda + S3 so I think we're significantly cheaper (+ Workers is faster than AWS lambda - R2 is still in open beta so not useful to compare perf against S3 yet). Yes, if you're using it to emulate public buckets, then it'll be a bit expensive (depending on egress charges you might otherwise face) 4. Soon. It's very high on our list alongside pre-signed URLs 5. Nothing to share at this time. 6. Yes. From Matthew Prince aka eastdakota [1] 7. Nothing to share at this time. [1] https://news.ycombinator.com/item?id=28682885 https://news.ycombinator.com/item?id=28682885

vlovich123 5y ago

1a. I don't think we have anything to share with regards to the logistics of putting cache in front of R2 or how that product will work. 1b. Unavoidably as you guess you'd be giving up the consistency. Presumably the consistency guarantees would be part of the cache-control header you associate with the object. Cache purging would probably work similar & we have exciting upcoming news about major performance improvements for that. But again, since we don't have any idea of what that product looks like, hard to say. 2. There is. I have a bunch of technical blog posts written but we decided to punt on providing that detail for a few months just to give everyone some breathing room. R2 does have one important extension we got the DO team to build just for us (not 1 instance of the code instantiated). That piece will only be available for R2. R2 is also driving performance improvements & API improvements to DO that will almost certainly percolate out to external users. 3. The equivalent model would be AWS Lambda + S3 so I think we're significantly cheaper (+ Workers is faster than AWS lambda - R2 is still in open beta so not useful to compare perf against S3 yet). Yes, if you're using it to emulate public buckets, then it'll be a bit expensive (depending on egress charges you might otherwise face) 4. Soon. It's very high on our list alongside pre-signed URLs 5. Nothing to share at this time. 6. Yes. From Matthew Prince aka eastdakota [1] 7. Nothing to share at this time. [1] https://news.ycombinator.com/item?id=28682885 https://news.ycombinator.com/item?id=28682885