Skip to main content

Traffic Manager Overview

Starting from today we have a mechanism that give us the possibility to control the traffic that comes to our Azure services. The name of this service is Traffic Manager.
What does this means?

Performance Load Balancing
Well, the simplest scenario is when we have a service running on different data centers. In this case we want to be able to redirect users to the closest data centers. We could have a service that identifies the location of the user and based on this redirect him to a specific data center. This problem is resolved by Traffic Manager Service. Using the client IP, this service will identify the location of the client and will redirect him to the closest data center (the one that have the lowest latency).
To be able to monitor the performance of each endpoint you will need to specify a relative path to the resource that is monitored. The monitor part is pretty simple, the latency time of each endpoint resource is measure every 30 seconds. When one of the request exceed 10 seconds or the return request code is different than 200 for more than 4 times in a row the endpoint will be considered down.

Failover Load Balancing
Another scenario that is cover by Traffic Manager is the case when one of our services from a data center is down. In this case the Traffic Manager will be able to detect the failover of the service and redirect the traffic to another data center. In this way all the traffic will be redirect to a backup service. We can define the order of the endpoints. This means that if the endpoint one will be down, the Traffic Manager will try to redirect the traffic to the second endpoint. If the second endpoint is down, the traffic will be redirect to the 3rd one and so on.
The performance Load Balancing also monitors the status of the endpoint and will not redirect traffic to an endpoint that is down.

Round Robin Load Balancing
This is the classic case of load balancing. In this case we have 2 or more endpoints available. The first client is redirected to the first endpoint, the second client to the second one and so on. This is a simple and very efficient way to make load balancing.
Also in this case, the Traffic Manager Monitoring component will redirect traffic to the endpoints that are up and running.

A normal question is when does the Traffic Manager appear on the requested map. For example if we have a domain and we will create a traffic manager domain named When a request will come to our website DNS name the request will be redirect to the Based on the policy that we use the traffic manager will redirect the client request to one of our endpoint.
Of course the latency of our system will increase at first request, but this value will be very low. In normal cases I would consider this value equal to zero and is not relevant for normal web applications.
Also, you should know that the resources of the endpoint that is used to check if the latency of the service needs to be over HTTP or HTTPS protocol. If your services works with different protocols that you need to add a HTTP or HTTPS resource – this can be a simple resource like a small file.
Another important thing to do after you configure the traffic manager is to update the DNS resource record to redirect the request from to
What do you think about this service? Do you think that you will use it in the near feature?


  1. It was about time to give traffic manager a new UI, since the old portal was a bit outdated..

    Anyway, why isn't possible to say to Azure: just route automatically the traffic to the closest available datacenter? (if I have the money to host a service in multiple data centers.. :) )


Post a Comment

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…