Skip to main content

Azure Redis Cache becomes more powerful with new features

There were a set of updates related to Azure Redis Cache last days.

If you didn't had the opportunity to use Redis Cache until now, you should know that it is a in-memory data structure stores that is used very often not only as a database or a cache, but also as a message broker. It is fully with features that can make  your life easier.
Microsoft is offering this feature as a out of the box service, that you can use it from the 1st moment, no configuration or installations needed.

Some new features are now appearing in Public Preview, that will make Azure Redis Cache more appealing to anybody.

Azure Redis Cache Clustering
Until now we didn't had to many options on Azure Redis Cache if we wanted more power from it or if we would reach the size limit of an instance.
Now, in the moment when we create a new instance of Azure Redis Cache we have the ability to activate this feature and specify the number of instances that we need. Don't forget that each instance (shard) from the cluster is in a primary&replica pair. The replicas are managed by Azure Redis Cache Service our of the box.

Don't forget that this feature can be activated only for new instances of Azure Redis Cache.
In this moment the maximum size of a shard is 53GB, combined with the size cluster that can reach 10. This means that you can have a Azure Redis Cache Cluster that has 530GB  ... WOW ...

Azure Redis Cache Data Persistence
How nice would be to be able to create backups and persistent your data from Redis Cache and to be able to access/restore it later on.
Even if it is a cache, you might need to be able to persist the data in case of a disaster. The persistence is done on Azure Storage and can be later used.

Azure Redis Cache LOVES Azure Virtual Network
Starting from now we can add our instances of Azure Redis Cache to Azure Virtual Networks (VNet). In this way we can isolate our instances of Azure Redis Cache from the public word.
By having the cache in VNet would guaranty you that nobody from outside the VNet can access it, if it doesn't has access to VNet.
This can be translated as an additional security layer at network level.

The new features that were just announced now for Azure Redis Cache makes this service very powerful and can be used with success for complex scenarios where the size of cache can be very big and requires to be isolated from public internet.


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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.