R2 is better for bigger files as it has the largest storage size. DO is good when you need all the d
R2 is better for bigger files as it has the largest storage size. DO is good when you need all the data to be synced across the global.
AEviction can happen on any plan but usually doesn’t happen unless there’s a Cloudflare update (about once a day in my experience), free plan users get evicted more frequently than paid/Enterprise. And yes it’s charged in CPU milliseconds instead of wall time.
DThank you 
.For a worker route, if you don’t setup any rate limiting
.What’s like the, default rate limit set to
KFree is 1000 reqs per min
KPaid doesn't have one (that limits the whole Worker)
QThose don't seem related though. 
What if I need small files (~2kB) that serve more as debug logs and will rarely-to-never be accessed?
What if I need small files (~2kB) that serve more as debug logs and will rarely-to-never be accessed?
HI would still go for R2. DOs are more for when you need compute attached to storage
KDurable Objects are stateful Workers that have transactional storage attached
KR2 is just object storage, strongly consistent with an S3 API
KBy far the simplest to use, since the S3 API means you can interact with it outside of Workers/the CF REST API
QI'm only using Workers to write the data, but I don't intend to read much from it.
QBut "compatible with S3" doesn't really mean much if I'm not using S3.
KMeans you can back it up easily, interact with it outside of Workers (i.e your own device), migrate to other storage options easily, etc
KIt's not about you using S3, it's about how many things integrate or work with the S3 API
QDon't both R2 and DO advertise as strongly consistent? If that's not a tie-breaker between them, what is?
QI'm not currently using, nor going to use, anything that integrates with the S3 API, so this doesn't help me choose between them. 
QThe limit page is a bit better than the differences page. 
Looks like R2 is for just dumping data into it [free tier + unlimited storage]. DO says it's a paid-only feature that limits you to 50GB for your entire account.
Looks like R2 is for just dumping data into it [free tier + unlimited storage]. DO says it's a paid-only feature that limits you to 50GB for your entire account.
U50GB is the initial account limit easy to raise
DI would go with Wasabi or Backblaze.
.ok thanks
JWorkers doesnt allow to change the content-length header or what?
KWhy would you want a custom Content-Length header? 
JI wanna use Workers to act as a middleman (for auth) between R2 and the client. The client is a machine that requires the files we store in R2.
JI wanna send those files once the client gets authenticated. However the client wont download the file if the content-length header is not correct
JJif you curl it, you can see the content-length is 15
JHowever, it should be 175104
CI'm seeing the file contains
[object Object] are you sure the file was uploaded to R2 correctly?KYeah, that wasn't uploaded right
JThats just the body
JTry it in a browser
CThat's how I got it
KBrowser or not doesn't change what the body is.
JI can download it without any problem from the browser. It doesnt show [object Object]
CTry opening the file
J
JIts a binary, why do you wanna open it?
KBecause it isn't.
KIt's text, that says
[object Object]KIt wasn't uploaded properly, the binary isn't there
JYeah
Jit was just me trying something
CGo to the R2 dashboard and download the file from there. Is it a binary file?
JThats the actual thing I have in the worker
DK