- EC2 Image Builder: Build your golden VM images on AWS - Wed, Jan 19 2022
- Configuring DFS Namespaces for Amazon FSx for Windows file servers - Fri, Jan 7 2022
- AWS Systems Manager Session Manager: Securely connect EC2 instances - Wed, Dec 22 2021
Azure Traffic Manager not only supports Azure-based services but also non-Azure based services. Therefore, it does not matter where you have your application whether it is on premises, Azure, or any other cloud.
Main features ^
If you're wondering what's unique about Azure Traffic Manager, check out the following reasons:
- Azure Traffic Manager ensures redirecting every received request to a healthy node. Therefore, in case one of the nodes is down, it will failover the traffic to another node.
- Clients will enjoy a lower access time to the application, which will redirect them to the nearest node or the fastest node in response. As a result, if you have clients around the world, you do not have to worry, since it will provide the best access experience to them.
- If you have multiple nodes, and you would like to maintain or replace any of these nodes, you do not have to worry about the downtime, since the service will direct the requests to other nodes. Therefore, the client will face no downtime.
- Microsoft offers Azure Traffic Manager for a reasonable price.
Routing methods ^
At the time of writing, Azure Traffic Manager supports six routing methods:
- Performance: This method routes the traffic to the fastest responsive node.
- Priority: This method routes the traffic to a specific node if the node goes down.
- Weighted: This method routes the traffic based on the weight assigned to each node.
- Geographic: This method routes the traffic to specific nodes based on the source location.
- Subnet: This method routes the traffic to a specific node based on an IP address range specified for the end users.
- Multivalue: This method routes the traffic to a specific number of nodes you can define, and all nodes will respond at the same time. This improves reliability in case the service did not handle the client request successfully.
The term "endpoints" refers to the nodes across which the traffic load balancing occurs.
There are currently three types of endpoints:
- Azure endpoints: This type is for Azure services, and it supports the following ones:
- Classic platform-as-a-service (PaaS) cloud services
- Web Apps
- Web app slots
- An Azure public IP (attachable to Azure VMs or Azure Load Balancers)
- External endpoints: This type is for public IP addresses or services hosted on premises or on any other cloud platform.
- Nested endpoints: This type is for sophisticated scenarios where you have a large environment and want to use different types of routing methods.
Create an Azure Traffic Manager profile ^
To create an Azure Traffic Manager profile, follow these steps:
- Navigate to Azure Portal > All Services and search for Traffic Manager profiles.
- Click on it, and it will open a new blade where you can click on Add to create a new profile.
- Then you will have to fill in some basic information, as shown below:
- Next, click on Create.
Configure endpoints ^
In the next step, you add your endpoints. In this article, I'll walk you through the process of adding web apps located in West Europe and the Central US to load balance the traffic between them.
Subscribe to 4sysops newsletter!
- Navigate to the Traffic Manager profile > Endpoints.
- Click on Add, which will open a new blade where you can specify the configurations that will fulfill your needs, as shown in the following figure.
- Next, click on OK. Then do the same steps again for your other endpoints.
- Finally, you can check all the endpoints you have added and their current monitoring status on the endpoints blade.
Azure Traffic Manager is a great service that allows you to distribute traffic to your endpoints with different routing methods using the Azure infrastructure that covers many areas across the planet.