0

Let's say we have an app deployed to Azure. App has external files not bundled with it, files which are required for app to operate. They are seperate but are essentially part of the software. Normally without a cloud service, we put these files on a disk path and tell the path to app using an environment variable.

Since writing to disk may be non persistent in a cloud environment, is this a case for using BlobStorage? Or is it for accessing files from anywhere, any app, in a manner similar to Dropbox? These files are not required to be available online, only the app needs to access them, so these kind of access is not required but also not appropriate.

Improve this question
1
  • I think you are talking about assets which should be bundled with App and should be served over CDN. BlogStorage can be used in case of File / Image upload to store the actual file / image and the URL in SQL. Commented Oct 27, 2016 at 5:09

1 Answer 1

Reset to default
1

Since writing to disk may be non persistent in a cloud environment, is this a case for using BlobStorage?

Generally, no. Blob Storage doesn't really make files available in the way that apps will want to use/consume them (plain old URI or file path). A more traditional CDN is a better fit for assets, and having the files as part of your cloud image deployment if they're dependencies.

It is kind of like Dropbox, but that's probably not the best way to think about it. Sometimes, your app needs to work with data that is too big to fit into SQL, and too unstructured to even fit into Table Storage. It's just some blob of data your app/users work with. That's Blob Storage.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.