Skip to main content

Azure Load Balancer and Sticky Connection (Source IP Affinity)

In this post we will talk about Azure Load Balancer and how we can have stick connection to our Azure Resources when we have multiple instances.

When we are using Azure VMs, Web Roles or Worker Roles and having multiple instances of the same type, all our requests will fly through a Azure Load Balancer. By default, Azure Load Balancer is not offering sticky sessions based on Source IP and Destination IP (see the last part of blog post).
This means that multiple requests that are coming from the same client are not guaranteed to end up to the same instance when port is changing. Based on different counters, like CPU level for example, Azure Load Balancer can decide to redirect a request to another instance.
There are cases when we need sticky connection and all the requests to end up to the same instance on Azure side. A good example is a relay server, where ports are changing for each request. In this case we need to be sure that all requests from the same source end up on the same instance.
Another example is for cases when we have a web application and we want all the requests from the same client to end up on the same instance, even when the requests are made using different ports (80, 8080, 443, ...)

In the above example we can observe that two different request from the same client, where the source port is different can end up on different instances.

Azure Solution
Azure Load Balancer supports this features, offering us the possibility to have sticky connections. This custom configuration of Azure Load Balancer is called Source IP. It allow us to bind a client to a specific instance from Azure. In this case, when we multiple instance in the backend, we will know that requests from the same client will end up on the same instance.

The bind between client and instance is formed by two types of tuples:
  • Client IP, Destination IP
  • Client IP, Destination IP, Protocol
Type of instances supported
In this moment there 3 types of instances that are support
  • Web Roles
  • Worker Roles
  • Virtual Machines 
, and load balancer endpoints.

How to configure
The configuration is very similar for all types of instances. We need to set the load balancer distribution to 'sourceIP'. 
Web/Worker Roles
This can be done from the .csdef file, in the moment when we configure the input endpoint. See below example:
<WorkerRole name="foo" vmsize="small" enableNativeCodeExecution="false">
    <InputEndpoint ... loadBalancerDistribution="sourceIP" />
Load Balancer Endpoint
This can be done using Power Shell, by setting the LoadBalancerDistribution attribute to 'sourceIP'

What we should be aware when using default Azure Load Balancer configuration
By default, Azure Load Balancer is using a tuple formed from 5 elements

  • (source IP, source port, destination IP, destination port, protocol type)
This means that we have a stick connection already, but the source port and destination port are used also to identify the instance. If we have multiple requests, with different port source or destination ports and we want to keep them on the same instance, that we should use Source IP Affinity.

In conclusion we should keep in mind what kind of sticky connection we need and what part of a request will define our sticky connection (IP, ports, protocol).


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 …

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.


Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms


Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming


Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…