Skip to main content

How you can deactivate session affinity on Azure Web App and ARR

In today's post we will talk about REST API and stick sessions.

Nowadays, REST API and Web Services are very common. We can find a lot of system and devices worldwide that are using HTTP(s) protocol and REST Services to communicate.
It not very common to send a cookie or session information when you calling a REST endpoint. All information are send in the heather, but not like cookies or session data.

In this situation you may want to disable sending cookies and session information to the clients. In this way you could use a little less resources on backend. Especially when you have a system that will need to manage hundreds of thousands of messages per second.
This two things can be manage and disabled pretty easily.

Going further, let's analyze what is happening when you host an endpoint like this on Azure like a Web App. It is important to know that in front of a Web App on Microsoft Azure we have out of the box a Load Balancer when multiple instances are deployed for the same Web App.
Behind this Load Balancer you will have of course an ARR (Application Request Routing). This feature is inherited from ISS - is one of the coolest extension of ISS.
ARR will keep track of different request. Once a request ends on a specific instance, the ARR will make sure that all other requests from the same client will hit the same instance of Web App.
This feature is important for application where there are session sensitive data or you have stateless connections. In this scenario you will always want to end up on the same instance.

But of course, not all the time you will need something like this. This feature is great when you need it. In most of the cases you will not need it. For this scenario, we can disable ARR to manage the session affinity.
The most easy solution is to set this configuration from web.config file, like below.
<configuration>
  <system.webServer>
    <httpProtocol>
      <customHeather>
        <add name="Arr-Disable-Session-Affinity" value="true" />
      </customHeather>
    </httpProtocol>
  </system.webServer>
</configuration>
There is another option, to set it from code, but it will require a deployment. Personally, I prefer to keep this kind this configuration in configuration files, where you can easily spot and change.
headers.Add(
     "Arr-Disable-Session-Affinity", 
     "True");

In this way we can reduce a little bit the stress that is on ARR system.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP