SALES: 1-800-867-1380

How to Use Caching

Updated: March 10, 2015

Azure Caching supports the ability to host Caching services on Azure roles. In this model, the cache is part of your cloud service. The following table describes the benefits of using role based Caching.


Characteristic Description

No quotas or throttling

Your application is the only consumer of the cache. There are no predefined quotas or throttling. Physical capacity (memory and other physical resources) is the only limiting factor.

Isolation, flexibility, and control

Co-located and dedicated topologies maximize your resources. You have as much control over Caching as you do over your own application.

Lower cost

There is no premium for cache. Pay only for the roles on which Caching runs. In a co-located scenario, you have already paid for the role.


Scale Caching in the same way that you scale your application: change the virtual machine size or the number of running instances of the role. It is also possible to create large caches (>100 GB).

Memcache support

Memcache binary and text protocols are now supported for easy migration of memcache-based applications to Azure.


Azure already locates role instances for a cloud service in proximity to improve performance. Hosting Caching on a role in your cloud service takes advantage of this fact to deliver low latency and high throughput.

There are two main deployment topologies for Caching: co-located and dedicated. Co-located roles also host other non-caching application code and services. Dedicated roles are worker roles that are used only for Caching. The following topics provide information on using the two topologies with the Azure Toolkit for Eclipse (by Microsoft Open Technologies).

For general information about caching in Azure, see Azure Cache.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft