Skip to main content

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

By
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.    
Labels:

Comments

Post a Comment

Popular posts from this blog

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

By
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(...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more