This document discusses caching services available on Windows Azure, including content delivery networks (CDNs) and caching. It describes how CDNs deliver content closer to end users, and caching stores frequently accessed data closer to Azure applications. Caching on Azure can be done through dedicated roles, co-location with applications, or shared caching services. The document outlines characteristics of CDNs like dedicated endpoints and worldwide datacenters. It also provides examples of caching configuration and workflows in Visual Studio and code samples for putting and getting items from the cache.
1. Windows Azure Caching
Pavlo Revenkov
EPAM Cloud Computing Competency Center
Email: pavlo_revenkov@epam.com
Skype: rp_risingstar
2. Caching services 2
CDN
• Delivering a “heavy” content closer to end user
Caching
• Storing frequently accessed data closer to Windows Azure application:
• Dedicated role
• Co-location
Shared caching
• Dedicated multi-tenant service
4. Main characteristics 4
Dedicated endpoint
• To work through the CDN you need to change storage services
endpoint to CDN endpoint.
Dedicated billing
• CDN usage is billable separately from storage services billing
World wide
• More than 20 CDN datacenters around the world
6. Caching 6
Two configuration models:
• Dedicated role
• Co-location
“Pay-as-you-go” only for compute resources
Several logical named caches
Ability to store session state and page output objects
10. References 10
How to use Windows Azure Caching
• https://www.windowsazure.com/en-us/develop/net/how-to-guides/cache/
Using Windows Azure CDN
• https://www.windowsazure.com/en-us/develop/net/common-tasks/cdn/
Differences between caching on-premises and in the cloud
• http://msdn.microsoft.com/en-us/library/windowsazure/gg185678.aspx