Workers would handle the request for an object.
This integrated compute layer can act like a proxy to enable “ slurp mode”. These kinds of use cases are already heavily dependent on CDN to meet the application’s requirements.īefore I go any further, here’s a link to the waitlist for Cloudflare R2.Īccording to a recent Discord Q/A with the Cloudflare workers team, Cloudflare R2 is going to be deeply integrated with Cloudflare Workers. Customer-Facing and Content-Driven: Usually doesn’t have heavy upload volumes but serves a mixture of graphics, text, searches.Real-Time Workflow: Product process-oriented use case that is receiving a lot of real-time data and then either displaying or analyzing it.Note that they are reading-heavy use cases: In order, here are the use cases that are most likely going to see huge improvements from moving to Cloudflare R2. The CEO at Cloudflare specified that these restrictions would not apply to Cloudflare R2 ( Terms of service link here, Hacker News comment here ). * Using Backblaze and/or Wasabi via Cloudflare CDN is limited: You can’t serve large amounts of media unless you’re paying more for your usage. ( Author's Note: We changed this paragraph based on an observant comment made on HN that pointed to a miscalculation)Īt a high level, the use cases that would suit Cloudflare R2 best are those where bandwidth costs are big enough to outsize the benefit of working with a provider with 3x cheaper storage, like Backblaze and Wasabi, who incidentally are part of the Bandwidth Alliance championed by Cloudflare that offers zero egress fees relevant to some (not all!) use cases*. Note that Cloudflare in their R2 launch post said “infrequent” storage operations, without specifying what those are and the rules that apply. Above this range, R2 will charge significantly less per-operation than the major providers.” - Cloudflare “R2 will zero-rate infrequent storage operations under a threshold - currently planned to be in the single digit requests per second range.
But, Backblaze B2 and Wasabi also have a bit of an answer to R2’s “zero egress”, which we cover in the next section.Ĭloudflare has also given itself wiggle room when it comes to the cost of read/write operations, although it’s implied that whatever it does should be very developer-friendly. Cloudflare R2 might shine better than other Amazon S3 alternatives when it comes to egress and read/write operations.Īt this point, we will take Cloudflare’s word for it: Egress will be zero cost. However, $0.015 per GB is not necessarily a deal-breaker here. When comparing Cloudflare R2 to Backblaze B2, Wasabi or Storj DCS, R2 is about 3 times more expensive for storage. Right now, Cloudflare R2 has cheaper and simpler pricing than several incumbent cloud services like Amazon S3 and Azure Blob, but is still well behind others on raw storage cost. If you think we're on to something, you just might be able to launch the next big thing with the help of Are the savings worth switching to Cloudflare R2?
0 kommentar(er)
