Which Azure Cache offering is right for me?
Updated: September 9, 2014
On May 12, 2014, Microsoft announced the availability of the Azure Redis Cache (Preview). We recommend all new developments use the Azure Redis Cache.
Azure Redis Cache gives customers the ability to use a secure, dedicated Redis cache, managed by Microsoft. With this offer, you get to leverage the rich feature set and ecosystem provided by Redis, and reliable hosting and monitoring from Microsoft.
Unlike traditional caches which deal only with key-value pairs, Redis is popular for its highly performant data types. Redis also supports running atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. Other features include support for transactions, pub/sub, Lua scripting, keys with a limited time-to-live, and configuration settings to make Redis behave more like a traditional cache.
Another key aspect to Redis success is the healthy, vibrant open source ecosystem built around it. This is reflected in the diverse set of Redis clients available across multiple languages. This allows it to be used by nearly any workload you would build inside of Azure.
Today Azure Redis Cache is available in Preview, in sizes up to 26 GB. The service will be Generally Available later this year. On General Availability, Azure Redis Cache will support caches larger than 26 GB and will have an availability SLA of 99.9%.
The Azure Managed Cache Service is currently Generally Available and offers an availability SLA of 99.9%. If you are an existing Azure Managed Cache customer, you can just continue using the existing service or choose to migrate to Azure Redis Cache if you wish to leverage any of the new features.
If you are self-hosting cache using In-Role Cache, you can continue to use In-Role Cache, or if you want to leverage the new features you can migrate to Azure Redis Cache.
Azure Shared Cache was retired on September 1st 2014. If you are an existing Azure Shared Cache customer, you should migrate as soon as possible. For Migration guidance, see Migrate from Shared Caching.