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
BIG-IP
Score 9.0 out of 10
N/A
F5 BIG-IP software from Seattle-based F5 Networks is a load balancing and application protection solution suite available on cloud or via virtual editions, on a subscription or perpetual licensing basis. The BIG-IP suite of products supports a wide range of security and application performance needs. The suite includes BIG-IP Local Traffic Manager (LTM) traffic management and optimization, BIG-IP DNS, BIG-IP Access Policy Manager (APM) identity and password protection, BIG-IP Application…
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 really do think it's well suited for any placement on the edge, especially with the WAF portion. APM is a whole different module unto itself that allows for VPN Connect connectivity, web top access. So it really is for these modules anyway, an edge appliance for us and not really usable in the interior of the network.
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
I think the policy configuration that had some improvements on the ASM word things, improvements may be on the signatures that would be good because it's a little bit confusing on the ASL, how they are updated and deployed, and this staging. So that's something that could be.
On the occasions when we've had to engage f5 support, they have been great. They have always resolved our issues quickly and been easy to work with and professional. The reason I give them a 10 out of 10, however, is because when we've had issues that have crossed over between the f5 BIG-IP, our Cisco switches, and our Microsoft IIS server the f5 support representatives have been extremely knowledgeable about every product and device involved and have been able to troubleshoot end-to-end without having to engage other vendors.
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 BIG-IP is my first F5 product that I have stared to work, and it brings me more experience doing a lot of migration upgrades from old code version to new code. The way F5 has all configuration help us to develop scrips to improve our process.
