Item — HN Reader

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.

1 comments

If you can cache your assets then the region typically doesn't matter too much (depending on workload).

That being said, I put up a spec to let you provide hints. We won't necessarily honor it today in some cases and in the future we may ignore it altogether, but the thinking is you provide the hint & can retrieve which geographic region the bucket is in.

We also have latency improvements coming down the pipe.

Vitali, how does serving directly from R2 via https work right now under the hood?

Is the data replicated across geos?

Does all or a portion of it get cached at a local edge once requested?

Does it basically behave as if it was handled by CF cache?

These parts are really confusing for me right now.