Hacker News Reader

Comment by ricopags | Hacker News Reader

We're onboarding to Cloudflare MagicWan and want to use them for logging, which they do to 's3-compliant' buckets.... on Google or Amazon.

I was pretty surprised at the lack of dogfooding, wondered if it's an oversight, on somebody's Gantt, or just not something R2 can handle for some reason.

View on HN

Yeah, the integration and production readiness of their non-core offerings is not perfect. I'm dealing with R2 and another service and you can tell they fell more like... specifically integrated features, rather than fully modular services you can choose to use as you want. Like the workers have possible R2 bindings, but you can't use those in a fetch() call - you have to use S3 compatible endpoint instead.

AWS has its own issues, but the push to have everything talking over API did wonders for the ability to use them as you want.

> Like the workers have possible R2 bindings, but you can't use those in a fetch() call - you have to use S3 compatible endpoint instead.

Sorry, could you please elaborate? Why can you not use a binding to an R2 bucket – and perform operations on its objects – in a `fetch()` handler of a worker? Or did I misunderstand this statement?

I meant that in your worker handler, you can only run fetch(s3-endpoint-for-bucket) rather than something like fetch(env.MY_BUCKET...)

This matters for their image resizing which needs to be used as options on fetch().

Reply on news.ycombinator.com