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.
N/A
F5 on IBM Cloud
Score 8.3 out of 10
N/A
F5 on IBM Cloud lets you see and control all traffic passing through your network. F5’s highly scalable, resilient and reusable services dynamically adapt to ensure application availability, performance and security.
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.
F5 on IBM Cloud has efficient ways to manage traffic, both local and that from the international sources. Besides, the firewall evaluations and management is handled by the program. F5 on IBM Cloud has a well designed virtual machine configuration, following both small and the largest templates for efficiency. The network configuration and monitoring is also deployed in the program.
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
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.
F5 on IBM Cloud is substantially competent in managing traffic, through network configuration and monitoring. The presence of a software security manager also suits the program for stability and confidence. Besides, F5 on IBM Cloud has an infrastructure management feature, which deals with storage, network, and the general hardware that supports systems.