Azure Redis Cache gives you the ability to use a secure open source Redis cache, managed by Microsoft, to build highly scalable and responsive applications by providing you super-fast access to your data. You also get to leverage the rich feature set and ecosystem provided by Redis while also getting reliable hosting and monitoring from Microsoft.
Important: The price in R$ is merely a reference; this is an int'l transaction and the final price is subject to exchange rates and the inclusion of IOF taxes and an eNF will not be issued.
Azure Redis Cache is offered in two tiers:
|Cache Name||Cache Size||Basic||Standard|
|C0||250 MB|| $0.022/hr |
| $0.055/hr |
|C1||1 GB|| $0.055/hr |
| $0.138/hr |
|C2||2.5 GB|| $0.09/hr |
| $0.225/hr |
|C3||6 GB|| $0.18/hr |
| $0.45/hr |
|C4||13 GB|| $0.21/hr |
| $0.525/hr |
|C5||26 GB|| $0.42/hr |
| $1.05/hr |
|C6||53 GB|| $0.84/hr |
| $2.1/hr |
Redis Cache is not available in the US Gov Virginia region. Please select another region.
Redis Cache is not available in the US Gov Iowa region. Please select another region.
Azure Cache is a family of distributed, in-memory, scalable solutions that enables you to build highly scalable and responsive applications by providing you super-fast access to your data. In addition to Redis, we also offer the following types of Azure Cache:
No. Azure Redis Cache units are standalone at the advertised sizes, either as a single node in Basic, or as a Primary/Secondary combination in Standard.
The concept ‘scale’ refers to the number of units of a particular type that a customer can purchase. It determines the maximum cache size provided by each tier, e.g. Basic can provide up to 1 GB, Standard can provide up to 10 GB and the Premium can provide up to 150 GB.
Upon reaching the scale limit, you have the option to purchase a higher level tier that better fits your cache size needs. For example, after hitting the 1 GB limit on the Basic tier, you would need to purchase the Standard tier.
Additional units of a tier have all the same price.
We don’t support the ability to create a managed cached in the portal today, you will need use the Azure Powershell SDK to create a cache. (The instructions can be found here.) Once you have created the cache you will have a full experience in the portal to manage it. We are currently evaluating options how to best bring this functionality back.
No. In-Role Cache can be deployed as a service alongside other application code in your web or worker roles. However, you can choose to have worker roles specifically dedicated to the cache and pay normal Cloud Services rates, which vary by the type of role and the role size.
Data transfers to and from the cache are charged at the regular rate.
We recommend new development use the Azure Redis Cache due to the flexibility it offers. It is based on the open standard Redis protocol that is supported by many programming languages (C/C++, .NET, Go, Java, Node.js, Objective C, Perl, PHP, Python, Ruby and over 29 more languages). This allows it to be used by nearly any workload you might build on Azure.
To support customers who made investments into Velocity Cache, who have dependency on it in their apps, to give them as much time as they need to move to the Redis cache.