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.

Conclusion
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.

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(

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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too