Storage Review

This is a quick post to review how the new storage setup would work. asd.

Assets Hosted on New Storage

The below two assets are hosted on GCP's blob storage. These assets use the "unique" naming scheme which is what we originally implemented but no longer require as it forces us to add a random string to the end of files uploaded. Update some more content.

Video

0:00
/0:20

Demo video taken from uploadVR

File Assets

A nice meatball recipe

Assets Hosted on Current Storage

The below two assets are hosted on our current storage infra and reflect how things are currently. They are the same as above.

0:00
/0:20

Same video as above

New Storage v2

The below two assets represent what storage will look like using Blob Storage. Both assets are loaded directly from GCP's blob storage (via Fastly for caching). The naming is the same vs standard disk based storage.

When assets with the same name already exist, -N is appended, eg meatballs.pdf -> meatballs-1.pdf -> meatballs-2.pdf etc etc.

0:00
/0:20

The one main change is that capitalization is lost. So Meatballs.pdf becomes meatballs.pdf. I don't think this is huge however.

New files

Subscribe to Staging Blog

Sign up now to get access to the library of members-only issues.
Jamie Larson
Subscribe