Azure on the Cheap posts focus on the architecture, techniques and technology in Azure that add considerable value without breaking the bank. This value is being measured in both the amount of effort...
Updated May 18, 2020
Version 1.0
Blog Post
Thanks for reading malecek and your comment. On each storage account, I enabled the CDN for the purposes of the test but as you point out the solution could be simplified if the initial cache miss is acceptable.
Azure Front Door, Traffic Manager, and CDN functionality do overlap a bit. I feel it is hard to beat Azure CDN for a static website on a budget. For dynamic websites and existing websites, AFD makes sense especially if WAF capabilities are required, and the simplicity of caching static content.
The example scenario is basically a static website with dynamic content coming from Functions. Your suggestion of using a single CDN with Traffic Manager routing to the closest function does make a lot of sense.
Any suggestions for the next post in the series? I was thinking of a comparison of repositories: Table Storage, Cosmos, and SQL.