an in-memory, distributed caching feature designed for Microsoft Azure applications.
A dedicated topology has the advantage of scaling the caching tier independently of any other role in the cloud service.
[5] For the best Caching performance, a dedicated topology is recommended because the role instances do not share their resources with other application code and services.
[3] In a co-located topology, you use a percentage of available memory on existing web or worker roles for Caching.
A co-located cache is a cost-effective way to make use of existing memory on a role within a cloud service.
[4] The following sections show Windows Azure Caching configuration and code examples.
If that does not succeed, the code retrieves the information with a database query and then stores the returned user data in the cache.
[11] Unlike co-located or dedicated topologies, the cache is not hosted on Windows Azure roles in a single cloud service deployment.
[13] In addition to storage capacity, each tier provides increasing processor and network capabilities.
In October 2012, support was added for hosting Caching on roles within a cloud service deployment.
These technologies share similar features, such as the assembly name, namespace, and types.