Skip to main content

I need a cache system, what service from Azure should I use?

On the market there are a lot of caching solution. The same thing is happening on Microsoft Azure. In this moment we have 4 different solution for caching (Azure Redis Cache, Managed Cache Service, In-Role Cache and Shared Cache).
A normal question that I heard from different people was: What kind of cache solution should I use?
This is a normal question, because having so many option you don’t know what to choose. I will try to describe what are the benefits of each cache solution that are available on Azure and see what we should use.

Azure Shared Cache
Azure Shared Cache is the oldest cache solution that was offered on Azure and is still available (for old clients) It was retired this year and can be accessed from Silverlight portal.
 This solution used to offer cache support as a service and I can say that I was able to use it with success on 3 or 4 project. The thing that I really enjoyed was the API, which was very simple to use and understand.

In-Role Cache
This cache solution enable us to host our cache system in Azure Roles. A great thing was that you could share a part of memory ram that was able on Azure Roles for cache. In this way you didn’t had to pay more for this resources – co-located topology.
If needed, you could even a dedicated role only for cache – dedicated topology. The biggest advantage of this solution was that you would could had the cache in the same role where your application would run – minimum latency.

Azure Managed Cache
When this cache service was launched, I saw him like Azure Shared Cache but with steroids. It is based on the same principle, cache as a service. This service added a lot of new features to the original cache solution especially from performance, scalability and security perspective.
When Azure Shared Cache retired, we were able to migrate to this cache service very easily. Under 2h, of working including testing (smile).
TIP: If you design your application as it should be, separating external services and resources from the core, you will be able to migrate very easily from one service to another.

Azure Redis Cache
Yes, Redis Cache. The open source one, that in this moment is used heavily in IT industry. You can have one or more Redis nodes with a cache size maximum to 53GB. What I like to this key/value store is that is very fast and you have a master/slave architecture, that offer you a persistent cache solution. Features like transactions, TTL (Time To Live) and sorted list are supported.
Imagine a service, based on Redis Cache, that is managed by Microsoft. You only need to use it. How great is that. It is important to know that is the same Redis Cache that is available as open source. It is not a custom implementation of it.

And now, the real question:
What kind of Cache solution should I use?

Well… even if the question sounds tricky, the response is pretty simple. All features that are available on all 4 solutions can be found on Azure Redis Cache.
Azure Shared Cache was already retired, so you should not use it. Azure Managed Cache is very similar with Azure Redis Cache, but without some features like atomic operation, list support, set operations (intersection, union, difference) and many more. From this perspective, Redis is much better than Azure Managed Cache.
In-Role cache can be cheaper than Redis, because you use resources that are in your roles, but from performance perspective, there is a huge difference between them. The last think why I didn’t use until now In-Role Cache is because of the SLA. You don’t have a SLA for In-Role cache because id running in your own roles.

Conclusion
If you start a new project in this moment you should go for Azure Redis Cache. Also keep I mind that cloud is very dynamic and separate cache service from your application as much as possible. In this way you will be open to change with minimum cost.

Comments

Popular posts from this blog

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&#…

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…