All geek questions in one place

Saving uploaded files to Azure websites: Azure file system or storage

When using Azure Website Sharing (WAWS), it seems that downloaded content, such as a photo or files, should be stored in Azure Storage Blob blocks, not in the WAWS file system.

Clearly, using Azure Storage is a great idea if you have a lot of data and require scalability and redundancy, however for small or simple sites this seems to add another level of complexity and also means that you cannot easily use such things, like ImageResizer without acquiring an Azure compatibility license, etc.

So, if products like WordPress from Azure Gallery use "/ site / wwwroot / wp-content / uploads /" to store all the downloaded files on WAWS, is there something wrong with using the WAWS file system for storage or is there other considerations to consider when using Azure WAWS?

+4
source share
2 answers

The main disadvantage of using the WAWS repository is that your data is now mixed with the application. By storing all your plugins / images / drops externally in a database or storage repository, you retain the flexibility to redeploy the application to a new region / data center by simply clicking your code on a new website and changing connection strings.

/ WAWS, , . - , , .

+3

Azure Web Sites Azure , , , . , , , - , .

, Azure Storage, , . - .

,

+2

Source: https://habr.com/ru/post/1539409/

More articles:


All Articles