Hey @User, this thread has been off-topic for a while as Andrew mentioned. And if you are so against our terms of service you are more than welcome to take your custom else-where. And seriously, if you are defending the Daily Stormer as a victim, you should seriously consider if this community is something for you. (Along with a raft of other life choices)

There is little ambiguity. If you serve regular website content/APIs etc, you can grow as large as you want. If you host things like videos, you will get a call eventually.. If predictability is an issue for you, AWS terms of service have no such clause so you could totally serve your site from there with any ambiguity?

Can't wait to see how well R2 handles metadata for millions of files. I've tried storing a dataset of around 25M tiny files on multiple Object Storage platforms and B2 is the only budget provider that can reliably list file metadata quickly.

To try and bring it back on topic, my original question was: What's the benefits of using R2 over backblaze and replicating files between their EU/US data centres? I'm assuming there'll be some nice integration with workers but curious if there's any statistics available around this yet.

1. Read again my comment, no one is defending The Daily Storm, that was just an example that your statement is not true, here is another one: https://deno.com/blog/02-03-2021-outage-post-mortem 2. The opposite of loving a product is not hating it but indifference, if I'm here giving examples of previous mistakes and consequences of ambiguous ToS it's because I think this is useful feedback for the R2 team.

They had said there are plans for tight Worker integration which will likely be of use if your application is entirely on CF. Regarding performance, its's still in quite early private beta so there isn't any stats known about that yet. I assume later in time there will be people who will compare, if Cloudflare themselves don't.

Not a ton is known at this point, but from a b2 perspective, it is most likely convenience.

i got a question about R2: is there going to be many locations for storage or is it going to be hosted in a single place?

Certainly not in a single place.

will we be able to pick the location or is it going to be like DOs are and be close to the initial upload?

Or will it auto-magically shuffle it around?

I got the sense it would be replicated like KV but not sure.

Cause that's a lot of colos.

Replicating object storage feels pretty massive

Yeah.

lord, that will get really expensive real quick

lets say about 100 or so colos can do that (not every colo can use DOs, im basing my theory on that), just uploading my avatar will take up 200MB globally

I'd hope either its choose-your-own-location, or its traffic-chooses-your-location

BUT, it would be fast

It will certainly not push things to all/most colos.

ah so like tiered cache? but with the file already there instead of fetched on request (also feel free to stop me if im digging too deep lmao)

But caching is colos is almost a necessity I would say.

Just to be clear, I know the very high level solution, but have no idea of details. We will have to see.

super excited to see the results either way!

Usually products like R2 are announced in the innovation weeks, when will be the next innovation week?

Undisclosed 🙂

They are always undisclosed until the Sunday morning US time 🙂

R2 Beta will be launched in Q2 and will be GA in the second half of 2022 according to the Q4 earnings call that is live now

Hey Dude, We've really gotta keep the anything at all related to earnings/stocks separate 🙂 That's why the other message was removed

This one is ok @User..