Windows Azure Cache
Windows Azure Cache is a distributed, in-memory, scalable solution that enables you to build highly scalable and responsive applications by providing super-fast access to data. Cache increases performance by temporarily storing information from other backend sources. High performance is achieved by maintaining this cache in-memory in a distributed environment. For a Windows Azure solution, Cache can reduce the costs and increase the scalability of other storage services such as SQL Database or Azure storage. ASP.NET applications can use Cache for the common scenario of session state and output caching.
Windows Azure Cache is available as a managed Cache Service (Preview), or you can create and manage Cache yourself using the Azure SDK with In-Role Cache.
Cache Service (Preview)
Windows Azure Cache Service (Preview) introduces a new way to perform caching by creating a dedicated cache for you in Windows Azure. This guarantees isolation of your business critical data and the performance of the cache is solely under your control. Cache Service (Preview) provides the ability to access the cache using a secure, publicly addressable endpoint. This gives you the ability to enable the following scenarios.
Use Cache from Windows Azure Web Sites.
Use Cache to share data across loosely coupled applications running on different cloud service deployments.
Use Cache to share data across multiple instances of the same application in different cloud service deployments.
Use Cache from Windows Azure Virtual Machines.
The Windows Azure Management Portal provides a host of management capabilities for Cache Service (Preview), allowing you to provision, configure, delete, and monitor the health of your Cache.
For more information, see What's New in Windows Azure Cache Service (Preview).
In-Role Cache supports the ability to host Cache on Windows Azure roles. In this model, the cache is part of your cloud service. One role within the cloud service is selected to host Cache. The running instances of that role join memory resources to form a cache cluster. This private cache cluster is available only to the roles within the same deployment. There are two deployment topologies for Cache: dedicated and co-located. In the dedicated topology, you define a worker role that is dedicated to Cache. This means that all of the worker role's available memory is used for the Cache and operating overhead. In a co-located topology, you use a percentage of available memory on application roles for Cache. For example, you could assign 20% of the physical memory for Cache on each web role instance. In both cases, you only pay for the Compute services required for the running role instances. For more information, see In-Role Cache FAQ (Windows Azure Cache) and In-Role Cache for Windows Azure Cache.
|The ability to host Cache on Windows Azure roles was officially released in the October 2012 release of the Windows Azure SDK. This is now a fully supported feature of Windows Azure Cache. To use Cache on roles, download the latest Windows Azure SDK and tools from the Windows Azure website.|
|Please note Windows Azure Shared Caching will be retired no later than August 29, 2014. In addition the Silverlight Portal used to manage this service will be decommissioned on March 31, 2014. Current Shared Caching users will receive communications on how to manage their shared caches if they choose to continue using this service after that date. For more information about migrating from Shared Caching to Cache Service (Preview), see Migrate from Shared Caching to Windows Azure Cache Service (Preview).|
Windows Azure Shared Caching is another option for using Cache in a Windows Azure application. Shared Caching is separate service where Cache is consumed as a managed service. Shared Caching enables you to register a cache through the Windows Azure Management Portal. Theses caches do not reside on your own roles. Instead, they reside on a group of servers in a multitenant environment. You can access your cache with a Service URL and Authentication token from the Management Portal. In this model, you pay for one of several cache offerings that vary in memory, bandwidth, transactions, and client connections. For more information, see Windows Azure Shared Caching.
In This Section
Other ResourcesWindows Azure Cache Service (Preview) How To