With the help of Azure Cache for Redis, you can use safe, open-source Redis Cache. Azure Cache for Redis is a dedicated service hosted by Azure which can generate highly scalable and highly responsive applications by providing ultra high-speed data access. You can also use Redis to offer abundant feature sets and ecosystem while obtaining reliable loading and supervision from Azure.
|The basic cache is a single cache node and is suitable for development/testing and non-critical workloads.||Production tier cache services based on master/slave replication.||Suitable for the Enterprise tier, and can be used for cache and temporary data. Exclusively designed for largest scale and enterprise integration.|
|Replication and failover||-||Yes||Yes|
|SLA||There is no SLA at the Basic||99.9%||99.9%|
|Configure Redis (Keyspace notifications, etc.)||-||Yes||Yes|
|Redis Data Persistence||-||-||Yes|
|Scale out to multiple cache units||-||-||Yes|
|Azure Virtual Network||-||-||Yes|
|Memory Size||250 MB - 53 GB||250 MB - 53 GB||6 GB - 530 GB*|
|Network Performance||Low - high||Low - high||Medium - highest|
|Maximum Number of Client Connections||20000||20000||40000|
|*More instances can be scaled upon request.|
Basic cache is a single cache node, suitable for development/testing and non-critical workloads. The Basic tier has no Service Level Agreement. During the update of cache node, the service will not be accessible and data may be lost.
|Cache Name||Cache Size||Basic||Network Performance||Number of Client Connections|
|C0||250 MB||¥ 0.14 Shard/Node/Hour (about ¥ 104.16 /month)||Low||256|
|C1||1 GB||¥ 0.35 Shard/Node/Hour (about ¥ 260.40 /month)||Moderate||1000|
|C2||2.5 GB||¥ 0.57 Shard/Node/Hour (about ¥ 424.08/month)||Moderate||2000|
|C3||6 GB||¥ 1.14 Shard/Node/Hour (about ¥ 848.16/month)||High||5000|
|C4||13 GB||¥ 1.33 Shard/Node/Hour (about ¥ 989.52/month)||Moderate||10000|
|C5||26 GB||¥ 2.66 Shard/Node/Hour (about ¥ 1,979.04/month)||High||15,000|
|C6||53 GB||¥ 5.31 Shard/Node/Hour (about ¥ 3,950.64/month)||Highest||20,000|
A replicated cache is provided in the primary/auxiliary configuration of two nodes. We will manage auto replication between two nodes, and provide a high availability Service Level Agreement.
|Cache Name||Cache Size||Standard||Network Performance||Number of Client Connections|
|C0||250 MB||¥ 0.35 Shard/Node/Hour (about ¥ 258.84 /month)||Low||256|
|C1||1 GB||¥ 0.87 Shard/Node/Hour (about ¥ 649.44 /month)||Moderate||1,000|
|C2||2.5 GB||¥ 1.42 Shard/Node/Hour (about ¥ 1059.16 /month)||Moderate||2000|
|C3||6 GB||¥ 2.85 Shard/Node/Hour (about ¥ 2117.50 /month)||High||5,000|
|C4||13 GB||¥ 3.321 Shard/Node/Hour (about ¥ 2470.82 /month)||Moderate||10,000|
|C5||26 GB||¥ 6.64 Shard/Node/Hour (about ¥ 4941.65 /month)||High||15,000|
|C6||53 GB||¥ 13.28 Shard/Node/Hour (about ¥ 9883.22 /month)||Highest||20,000|
In addition to all standard level features, the new Premium tier includes even more other features, e.g.: performance superior to basic or standard tier caches, bigger workload, disaster recovery and enhanced security. Other features include:
- Redis Persistence allows you to save data stored in the Redis Cache. You can also obtain screenshots and back up data, so as to upload them in case of failure.
- Redis Cluster automatically segments data in multiple Redis nodes, thus you can create a workload (bigger than 53 GB) with bigger memory and obtain better performance.
- Azure Virtual Network (VNet) is deployed to provide enhanced security for Azure Cache for Redis, and also offers subnet and access control policies and further limits other access features.
|Cache Name||Cache Size||Pricing of official edition||Network Performance||Number of Client Connections|
|P1||6 GB||¥ 3.72 Shard/Node/Hour (about ¥ 2770.51/month)||Moderate||7,500|
|P2||13 GB||¥ 7.44 Shard/Node/Hour (about ¥ 5534.69/month)||Moderate||15,000|
|P3||26 GB||¥ 14.88 Shard/Node/Hour (about ¥ 11069.38/month)||High||30,000|
|P4||53 GB||¥ 29.77 Shard/Node/Hour (about ¥ 22150.52/month)||Highest||40,000|
|P5||120 GB||¥ 63.92 Shard/Node/Hour（about ¥ 47556.48/month）||Highest||40,000|
How are we charged for data transferred to and from the cache?
Data transferred to and from the cache are charged at the normal rate.
Can I scale the Azure Cache for Redis Unit (similar to the concept of a Hosted Cache)?
Yes. You can expand to multiple Redis Cache Units at the Advanced level.
Which kind of cache will be used if I want to create a new cache in Azure?
Deploying Azure Cache for Redis is recommended due to its flexibility. This cache is based on an open standard Redis agreement supported by many programming languages (C/C++, .NET, Go, Java, Node.js, Objective C, Perl, PHP, Python, and Ruby, as well as over 29 more languages). Thus, almost any workload generated in Azure may use this cache.
Since you recommend using Redis, why the recommended “Hosted Caching” option is not provided?
This aims to support the customers, who invest in the Shared Caching they rely on, giving them sufficient time to migrate to Redis Cache.
Is the storage billed separately?
Yes. Premium Redis supports Redis Data Persistence, if customer set Data Persistence in Premium Redis, the storage will be charged separately.
the bill of storage depends on the storage type customer selected. If he/she selected SSD, the storage would be charged based on the price of SSD; if he/she selected HDD, the storage would be charged bases on standard page blob.
Support & SLA
If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.
We guarantee that the customers have connections between the cache terminal and Internet gateway at least 99.9% of the time. To learn more about the details of our Service Level Agreement, please visit the Service Level Agreements page.