Shulou(Shulou.com)06/01 Report--

There are currently three routing options available in Azure's traffic manager. Although you can choose any routing method at any time, each traffic manager profile can only use one routing method at the same time. It is worth noting that all traffic routing methods include endpoint monitoring. After configuring the traffic manager profile to specify the traffic routing that best suits your needs, you need to configure monitoring settings. When monitoring is configured correctly, the traffic manager monitors the status of endpoints, including cloud services and Web sites, and does not send traffic to endpoints that it considers unavailable. The three traffic manager traffic routing methods are as follows: (for ease of understanding, scenarios are all cited here) 1, failover: you have nodes in the same or different Azure data centers and want to specify certain nodes to send all traffic first. In the event of a failure of the specified node, immediately switch to the backup node. In this scenario, you can choose to fail over. 2, round robin: when you want to distribute the load between nodes in the same data center or across different data centers, you can choose round robin. 3, performance: when your access comes from different geographical locations, you want the client to use the "nearest" node to access, to achieve the lowest latency, you can choose performance. It is important to note that the website on Azure (website) itself provides the ability to fail over and loop traffic routing in the same data center, regardless of the pattern of the site. The traffic manager allows you to specify that your site's failover and recurring traffic are routed to different data centers. The method of failover traffic routing usually requires an organization to ensure the reliability of providing services. This is mainly achieved by switching to the backup node immediately when the primary node goes down. A typical application scenario for failover is to provide the same set of nodes and send traffic to the primary node and to one or more backup nodes at the same time. If the primary node is not available, the client that sent the request will be redirected to another node in turn. If the first standby node is not available, it will point to the second and third node until an available node is found. When configuring the method of failover service routing, the order in which endpoints are selected is important. When configuring the method of failover service routing, the order of the selected endpoints is important. A common round robin routing pattern is to provide the same set of nodes to send traffic to a node in a continuous loop. It randomly selects the fastest node and does not send traffic to the detected unavailable node. Round robin also supports weighted allocation of network traffic. Round-robin weighted allocation allows your load to be allocated based on the allocation weights of each node. The higher the weight, the more frequently it is accessed. The scenarios available for this method include: 1, step-by-step application upgrade: assign the routing percentage of traffic to a new endpoint, and gradually increase the traffic to 100% over time to complete the application upgrade. 2, application migration to Azure: create profiles for both Azure and external endpoints, and specify the weight of traffic routed to each node. 3, explosive growth: quickly deploy to the cloud through the traffic manager profile to cope with explosive growth. When you need extra capacity in the cloud, you can add or enable multiple endpoints and specify which parts of the traffic go to each endpoint. At this point, you cannot configure weighted traffic routing using Azure's classic portal. Azure provides programmatic access to this method using PowerShell commands for managing REST API and Azure using related services. If you want to test the profile of a single client and see if it is equal to weighted round robin behavior, verify that DNS name resolution is based on the same or different IP address of the weighted value endpoint in the configuration file. When testing, you must first disable the client-side DNS cache or clear each DNS cache that attempts to ensure that a new DNS name query is sent. In order to distribute traffic to nodes located in different data centers around the world, the performance routing method can directly import traffic to the nearest node to ensure the lowest latency between clients and endpoints. In general, the "nearest" endpoint is directly equivalent to the nearest geographic distance. The method of performance traffic routing allows you to allocate traffic based on location and delay, but does not take into account real-time changes in network configuration or loading accounts. The performance routing method is to find and request the node closest to the client. The nearest node here is determined by the Internet latency and the round trip time between each IP address and each data center. It is updated at periodic intervals and does not mean that it is a real-time reflection of cross-Internet performance. It does not take into account the load of a given service, even though the traffic manager monitors nodes according to the method of your choice and does not include DNS query responses if they are unavailable. In other words, performance traffic routing also uses the method of failover traffic routing.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.