Azure Traffic Manager routing methods
When the Traffic Manager receives the DNS query from the clients, it does not directly send it to the service endpoint, but it checks which routing method is being used, and based on that method it will determine to which service endpoint the request will be directed.
Azure Traffic Manager supports the following four routing methods:
- Performance: This method routes the client queries to the nearest endpoint based on the geographic location to the client, which will provide a better performance for the client because it follows the lowest network latency model
- Weighted: This method routes the client queries based on a weight that you define
- Priority: In this method, the queries will be queried to a primary service endpoint, and if it goes down, it will be redirected to a backup service endpoint
- Geographic: This method detects the region from which the DNS query is originated and redirects it to a specific endpoint
