In-Role Cache for Azure Cache
Updated: August 9, 2013
In-Role Cache on Microsoft Azure Cache allows you to host Cache within your Azure roles. This cache can be used by any roles within the same cloud service deployment.
Cache provides several benefits to application developers. Cache increases performance by temporarily storing information from other backend sources. High performance is achieved by maintaining this cache in-memory across multiple cache servers. For a Microsoft 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.
There are two main deployment topologies for In-Role 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 (Azure Cache).
|The ability to host Cache on Microsoft Azure roles was officially released in the October 2012 release of the Microsoft Azure SDK. This is now a fully supported feature of Microsoft Azure Cache. To use Cache on roles, download the latest Microsoft Azure SDK and tools from the Azure website.|
Microsoft Azure Shared Caching is another option for using Cache in a Microsoft 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 Microsoft 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 Azure Shared Caching.
|For a good overview of Microsoft Azure Cache and caching concepts, watch the following two TechEd 2012 talks.|
In This Section