Need a low-cost inbound traffic management and load balancing solution? Want to set it up in minutes? Azure Traffic Manager is your best option
November 08, 2021
Need a low-cost inbound traffic management and load balancing solution? Want to set it up in minutes? Azure Traffic Manager is your best option
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Azure Traffic Manager
Azure Traffic Manager is our primary site availability and performance solution for all services we provide to our employees. We have a complex setup with multi-sites and a cloud region, and inbound traffic hit multiple locations, we have multiple [Azure Traffic Manager] configuration for numerous services, for example, for services offered from multiple locations, we have region-based configuration that returns the nearest endpoint for clients. Additionally, we use [Azure Traffic Manager] to provide High Availability across multiple regions, downtime hits 30 seconds in case of a failure with a connected client, which is considered minimal for us, users are then directed to the next healthy endpoint. [Azure Traffic Manager] is considered an essential part of our setup, without it, many of our business services will be affected and many more complex technologies would be required
- 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
- 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
- Performance DNS Load Balancing
- High Availability for Services across Multiple Datacenters
- High Availability & Load Balancing for Inbound Traffic Across Multiple Internet Links
- 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
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.
Do you think Azure Traffic Manager delivers good value for the price?
Yes
Are you happy with Azure Traffic Manager's feature set?
Yes
Did Azure Traffic Manager live up to sales and marketing promises?
Yes
Did implementation of Azure Traffic Manager go as expected?
Yes
Would you buy Azure Traffic Manager again?
Yes