3 ms·
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
by 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