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
Google Cloud DNS
Score 8.9 out of 10
N/A
Google Cloud DNS is a managed DNS service, featuring a global network of anycast servers and touting reliability, availability, and performance.
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.
Google Cloud DNS is well suited in most cases - it has a clean interface, plenty of configuration options, available to view and edit on the Google console.
It may not be as well suited for novice users since the documentation about the various fields is not always available near where the fields need to be set.
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
This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.
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.
Google Cloud is the easiest to use sharing platform available. Other platforms are not as accessible as accessing the Google drive when you are logged in with your Google account. Trello has a limited sharing capacity which I have not experienced with Google Drive. Our institution has afforded us unlimited space on the Google Cloud platform which was more of a struggle to obtain on Dropbox. Teams would select and use Dropbox voluntarily and have to arrange payments and claims. I also find that Dropbox sends a multitude of emails regarding storage and upgrades while Google Cloud is generally silent but highly effective as a storage tool
