Static Content Hosting

Deploy static content to a cloud-based storage that can deliver them directly to the client. 

When to use this pattern?  

• Minimize the hosting cost for Website compute Service  

• Expose static content for applications running on-prem  

• Locating content in more than one geographical area  

• Monitoring cost and bandwidth usage 

When NOT to use this pattern?  

• Web Application needs to perform some processing on the static content before delivering it to the client.  

• The Volume of the static content is very small 

Considerations  

• Storage Service supports HTTP/HTTPS  Content Delivery Network (CDN) for maximum performance  Storage accounts are geo-replicated, so IP might change, use URL instead  

• It’s challenging to have some static content in Storage account and some static content in compute service.  

• Storage services must allow public read access, but it’s important to disable public write access  

• Consider Valet key Pattern to control access to resources