Cache Offerings for Azure Managed Cache Service
Updated: August 25, 2015
|Microsoft recommends all new developments use Azure Redis Cache. For current documentation and guidance on choosing an Azure Cache offering, see Which Azure Cache offering is right for me?|
Managed Cache Service provides Basic, Standard, and Premium cache offerings, each with a different set of options, sizes, and pricing, which allow you to configure exactly the right cache for your application. This topic provides an overview of the available cache offerings and how to configure the desired cache offering for your cache. For information about pricing, see Cache Pricing.
Managed Cache Service provides the following three cache offerings.
The Basic cache offering is available in sizes from 128MB to 1GB, in 128MB units. Basic caches are hosted on shared hardware and support a single default named cache, which is configurable for expiration and eviction.
The Standard cache offering is available in sizes from 1GB to 10GB, in 1GB units. Standard caches are hosted on dedicated hardware, and support up to 10 named caches including the default named cache. In addition to the features included in the Basic tier, Standard caches also supports notifications and high availability.
The Premium cache offering is available in sizes from 5GB to 150GB, in 5GB units. Premium caches are hosted on dedicated hardware, and support up to 10 named caches including the default named cache. The Premium cache supports all features of Basic and Standard caches, including support for notifications and high availability.
Cache offerings can be configured when a cache is created, and as the needs of your application change they can be changed on the Scale tab for Cache in the Management Portal.
For more information about choosing a cache offering when creating a cache, see How to: Create a Cache for Azure Managed Cache Service.
The cache offering of a running cache can be changed in the Scale tab for Cache in the Management Portal. Note that when changing cache offerings, all cache data is lost.
For more information about changing the cache offering of an existing cache, see Scale a Cache for Azure Managed Cache Service.