Azure Traffic Managerの評判・口コミ 全1件

What do you dislike about the product?

Availability monitoring works only with 200 OK responses from web server. No customizable port forwarding through traffic manages

What do you like best about the product?

Traafic manager is a very simple but powerful tool, that managing user connections to public facing resources. It can be used to direct users to most geographically close endpoint of your application, to direct all users to primary endpoint and switch to secondary one if primary in not available, also it can balance connections between several endpoints to avoid channel overload. It can work for both Azure or on-premise locations, provides availability monitoring for your endpoints. All endpoints remains available with only one URL. It can be used in conjunction with Azure Site Recovery, to make failovers completely transparent for end users. Users will access the same URL regardless of current active location of your resources.

Recommendations to others considering the product:

Try using this instead public facing load balancer, it will save your costs

What do you dislike about the product?

Working fine with web facing applications only and can`t be used for administrative work on resources. It also increases response time of your resources.

What do you like best about the product?

Traffic Manager acts as single point of access for different instances and location of your application, it redirects users to most appropriate endpoint according to it`s settings. You can send traffic to instance with closest location to user, or balance multiple requests between all endpoints, or send traffic to prioritized endpoint and redirect to secondary one, if primary is not available, so it acts as a part of high-availability solution. It also has monitoring capabilities, you are able to see which of your endpoints are currently available. Using traffic manager in failover mode with disaster recovery solutions making these easier to end users, as they can access single URL and not think where is your application is currently running. Solution is vary stable and easy to deploy and configure, it works with both Azure and on-premise environments, so implementation does not requires any changes in your current infrastructure

Recommendations to others considering the product:

Ensure that monitoring is configured correctly, or you can send your users to inaccessible endpoint

What do you dislike about the product?

Implementing traffic manager can increase initial response time of site because it makes request route longer

What do you like best about the product?

Traffic manager allow redirecting users to appropriate endpoints based on different settings. We are using it to route users to national versions of site, depending of users location. It allows users to see information on their native language and minimize response time of web pages, because national sites are located in nearest datacenters. The main feature that entire routing is performed in a backgroud and all users could use single URL to access the site regardless of their location. The second great feature is failover option, so site remains available with the same URL regardless of it`s current location. We are using it for on-premise sites where Azure Site Recovery was configured for servers. URL remains live even after failover to Azure

Recommendations to others considering the product:

I can recommend to implement it if you have many national versions of your site, located internationally. This will make user access easier

What do you dislike about the product?

Increases initial response time for site, because of routing activities. Even if users being redirected to closest site initial request will go to Azure region where traffic manager is deployed

What do you like best about the product?

Great solution for routing user connections to closest endpoints, decreases load for each instance of your applications and allows users to access national versions of site using the same URL regardless of users location. Simple monitoring option allows to track availability of your instances and re-route users in case of outages. Simple to deploy and maintain, very stable solution that allows you avoid many incidents related to response time and availability of your application.

Recommendations to others considering the product:

It could act as public facing load balancer for instances deployed in the same region. It also can handle stateful application without additional tuning

What do you dislike about the product?

Pricing is dependent on the the number of data points being used for traffic views, endpoints being monitored which affects the overall cost.
Load balance option can be used for many scenarios.

What do you like best about the product?

1. The improvement in application response time as the traffic manger directs the traffic to the endpoint with lowest latency in the network.
2. Maintenance with no downtime

Recommendations to others considering the product:

Good options for load balancing within Azure .

What do you dislike about the product?

The learning curve is difficult for new employees. They are slow to learn how to use it.

What do you like best about the product?

Azure is the most reliable traffic manager ive ever used. I have yet to experience issues from traffic thanks to azure

What do you dislike about the product?

We had an issue where all of our endpoints went offline.

What do you like best about the product?

Traffic manager takes an old technology (DNS) and adds new flair to it

Recommendations to others considering the product:

Make sure you read the documentation and fully understand what traffic manager does. My team struggled to understand that network traffic does not actually flow through traffic manager. It is just DNS queries, that's it!

What do you dislike about the product?

Honestly, it's not as intuitive as i'd like and a majority of the time I am forced to google multiple things. Azure Traffic Manager offers only limited health check options. Azure Traffic Manager’s HTTPS health check only accepts HTTP 200 OK responses as valid. Most TLS-based VPNs will respond with an HTTP 401 Unauthorized, which Azure Traffic Manager considers “degraded”. The only option for endpoint monitoring is a simple TCP connection to port 443, which is a less accurate indicator of endpoint availability.

What do you like best about the product?

The multiple traffic routing as well as the privacy involved with the traffic routing. I like how the Traffic Manager does not see the HTTP traffic between the client and the server. And it's nice how there's an automatic notification when streamline processes fail and how everything is on the cloud.

Recommendations to others considering the product:

Give it a try, it has a great GUI.

What do you dislike about the product?

Price is high when compared to other competitors.

What do you like best about the product?

More helpful in the analytical solutions and migration of the data