Likelihood to Recommend 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.
Read full review The service is really well-suited for pretty much any site that is primarily display-driven (that is, mostly GET requests). The network is able to handle massive volumes of traffic and their POPs have spread out pretty much anywhere that it's easy to get them (so basically everywhere but China and Russia). My team witnessed several large-scale attack attempts on some high-profile websites (attacks in the 10s of millions of requests per second) that were mitigated before ever coming back to the actual application; in one case we didn't realize the attack had happened until we looked at the logs the next day. Because it's a cache store option, the default configuration does not cache POST responses, and it can be difficult to set up things like authenticated paywalls as a result.
Read full review Pros Performance DNS Load Balancing for Lowest Latency Endpoint to Clients Priority-Based DNS Load Balancing to ensure maximum up time for a service Geographic-based DNS Load Balancing to force certain clients in certain regions to connect to specific endpoints Read full review Very performant and fast -- major companies have drastically reduced page load times with Fastly's edge technology. Support for many types of media, including video. Image add-on makes serving and manipulating images very simple. Read full review Cons 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 Read full review WAF is hard to configure. No comprehensive rate limiting without a pricey upgrade. Account access controls are extremely limited. Read full review Alternatives Considered 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.
Read full review It’s the fastest and most configurable.
Read full review Return on Investment Service cost is exceptionally low Overall, this product saves a lot of money for the value it provides and it isn't expensive It's around half a dollar per million queries, which is truly peanuts, extras may be required if you do advanced configuration I can't see any reason why any business wouldn't be using this product, very low investment for a very high return and savings Read full review Fastly dramatically reduces load times for clients all over the world thanks to their global system of POPs. Fastly is a cost-effective choice when a highly-performant CDN is required and makes it simple to support data that is quickly invalidated. Read full review ScreenShots