Microsoft offers a content delivery network, Azure CDN.
N/A
Azure Traffic Manager
Score 9.7 out of 10
N/A
Microsoft's Azure Traffic Manager operates at the DNS layer to quickly and efficiently direct incoming DNS requests based on the routing method of your choice.
Azure CDN has at hand an infinity of applications and tools to implement in your system and have better control of your data in a clean and secure platform on the web, we recommend this program since the percentage of solutions provided by this program is very high and find a way to make each user's job easier.
Azure Traffic Manager is a great product, if you have multiple sites hosting similar services (Primary and DR), and you want to ensure that users are directed to the DR in case of a primary datacenter failure, [Azure] Traffic Manager does this very nicely. If you have a service hosted across multiple regions/datacenters and you want to balance the inbound load between the regions, [Azure] Traffic Manager does this very well, of course such scenario would require a database replication or something like Cosmos-DB in the backend [Azure Traffic Manager] is also well suited for inbound traffic with multiple IPs, you can fail-over traffic from one inbound IP to another based on its availability, or if you have multiple internet connections that you want to balance the load across, it does this pretty nicely too.
I found the CDN very easy to setup and configure within the Azure Portal.
Being Azure, there are plenty of free tools that allow you to manage the CDN from a UI that is not the portal. This was especially handy when I trained end users how to manage content within their specific realm.
Traffic View is a great feature, but doesn't work very well, sometimes it gets stuck and stops loading traffic view data
Automatic probing for endpoints sometimes gets stuck too, I would recommend a technique to test the endpoint in real time from Azure Portal
Traffic View heatmap is buggy and doesn't point correctly to locations
Traffic View portal doesn't show source countries (Shows coordinates) it would be much more helpful to have coordinates auto-translated to geolocations/countries
Great support from the team whenever we're stuck. Very proactive in resolving issues and also making changes as per the requirements of the organization.
Amazon Route 53 Traffic Flow does what [Azure] Traffic Manager does, however, in Azure Configuration is separated between Azure DNS Zones (For DNS Zone Management) and [Azure] Traffic Manager for DNS Traffic Management and Load Balancing, Route 53 in a unified product for DNS Traffic Management using Traffic Flow and DNS Zone Management. Route 53 does a great job, however, we found it to be a little bit more complex to setup than [Azure] Traffic Manager, Setting up traffic manager is pretty easy even for the first time, and getting the best out of it is relatively simple.
Azure CDN reduced origin instance load by removing the need to constantly serve large numbers of static files, meaning applications can be deployed with smaller/fewer instances.
Azure CDN reduces apparent load times to customers by serving cached files out of POPs in the local region of those clients, instead of requiring those clients to make multiple, lengthy requests through to the origin servers.
