Open D3v0nM opened 5 years ago
I think an Application gateway, because that way we can automate it and get that beer. But i'll try and find some kind of objective analysis and see if i can truly figure out which is better.
Beginning research, going to hunt down what needs to be certified (which endpoints in Azure) and then look at applying either CDN or an Application Gateway.
Estimated time: 20 hours
Here's a screenshot of the endpoints that Devon configured:
Update:
See subsection: Enable Azure CDN for the storage account. That's the first step.
Okay so in terms of comparing application gateway to CDN, this is the description of CDN from Azure when i was going to enable it on dev storage.
The Azure Content Delivery Network (CDN) is designed to send audio, video, images, and other files faster and more reliably to customers using servers that are closest to the users. This dramatically increases speed and availability, resulting in significant user experience improvements.
Created an Azure CDN profile for kicks but, it doens't look like it serves any purpose since we can enable CDN directly on the storage account. I'm going to hang onto it for a bit and make sure.
Update: Scratch that looks like we do need the profile, onward!!!
CDN is not what we need as we do not have a large scale application that will have large numbers of people uploading data. What we need is an application gateway.
Brad and Devon configured an application gateway here:
But there are issues with routing that will not be resolved before the presentation Tuesday, so we will not be using it in the final build.
You can find a general write up here:
That's a general guide to the process of using CDNs to associate an endpoint. We took a different approach though and choose not to use a CDN profile and instead created individual CDNs at the resource.
Do we need CDN or App Gateway in front of our site to control logic of which page/Function is loaded?