Skip to main content

In-Role Cache and Azure Managed Cache Services will be retired next year

A few days ago Azure team announced that they will retire Azure Managed Cache and In-Role Cache will not be supported anymore. In this post we will take a look on why this is happening and what could this decision affect us.
The official announced can be found on the following link: https://azure.microsoft.com/en-us/blog/azure-managed-cache-and-in-role-cache-services-to-be-retired-on-11-30-2016/

Azure Managed Cache Services is a service that allow us to use a cache solution as a service. From our application, we would only need a 'connection string' to the cache services. Using this information we could store or retrieve any kind of content from cache.
In-Role Cache allows us to cache content in the memory of our role (web/worker role). A part of the memory can be configured to be used for cache. The data that is cached in In-Role Cache is synchronized automatically between multiple instances of our role.
This two cache solutions offered by Microsoft Azure are used very often by small to medium size application that needs a simple solution to cache content.
I'm using Azure Managed Cache in 6 application that are hosted on Azure and works great. The cache is not super fast, but it is enough for the use cases that we need to cover. For cases when we need to be super fast and we have a more complex use case we use Redis Cache. Personally I never used In-Role Cache in production. I played with it on different occasion, but nothing more than that.

From November 30, 2016 Microsoft Azure will retire Azure Managed Cache Service completely. This means that if you are using this service that you should start to plan and prepare a migration to another cache service like Azure Redis Cache. On the same date, the support for In-Role Cache will end.
It is important to know that on all public Azure Regions, China and US Government Datacenters , Azure Redis Cache is available and ready to use.

A normal question is: 'Why this is happening?". This is happening because both services of cache are using Windows Server AppFabric 1.1, for which the support will end next year. It is normal that all services that are constructed over AppFabric 1.1 features to be affected.

The migration from Azure Managed Cache Service or In-Role cache to Azure Redis Cache can be made easily. Not only this, but all features that were available in this two cache solution can be found in Azure Redis Cache. There are some small things that cannot be ported directly 1 to 1, but are isolated and simple to migrate. A post about this topic will come next week.

Even if this change may affect some clients, overall this is a good change. From a cache perspective, there were a lot of options on Azure, with similar performance and features. For clients is pretty hard to decide when you have 2 or 3 services with the same functionality, features and costs.    

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