7 Replies
Hey
I just created an R2 account and I'm looking at it now.
It seems like it has built-in CDN-like features that distribute the content based on the users' location.
I'm reading your migration docs now
This Sippy method, will copy the data, not hard-transfer, correct? There is no chance of the source data being corrupted using this method, right?
So R2 data is only stored in one region but you can cache it with the CDN. The CDN has cache in every single datacenter (they dont share cache and cannot enable tiered cache yet).
As far as sippy yes it will do a request -> serve & copy. Data will never be corrupted on your own S3 (you shouldnt even need to give write access afaik) for sure and shouldnt ever have issues on R2.
Awesome
yeah I just taught myself web development over 2 years to get my company un-addicted to development firms. I got us off of WP and onto a Next.js/PlanetScale/Render.com jam stack and we couldn't be happier. We're using the S3 just to preserve the content's folder-structure from WordPress. (for example awsbaseURL.com/publicbucket/wp-content/2023/December/23/someImage.jpg).
Object servers are the correct "server-type" to be distributing everything from blog images to our downloadable software, correct?
Or am I greatly mistaken/misguided? I've heard of things like lambda functions, etc...
"correct" is not the word I would use as there are millions of options that can work. R2 is a fine store to use for images and downloadable software.
ok yeah, but we have 10 years of blog articles that we need for SEO, from my research it seems like an object server is the only thing that would preserve those folder structures for the old content. I guess we could use something more modern for all new content.
Am I correct in believing object servers are the easiest/cost-effective way to preserve those old folder structures?
They can be yes
ok thanks