Windows Azure SQL Database Marketplace
What is the Windows Azure Content Delivery Network (CDN)?
The Windows Azure CDN is a global solution for delivering high-bandwidth content hosted on Windows Azure. The CDN caches publicly available objects at strategically placed locations to provide maximum bandwidth for delivering content to users.
What is Windows Azure billing in general?
The Windows Azure CDN is a pay-per-use service. As a subscriber, you pay for the "amount" of content delivered. This article will discuss how customers are billed for using the Windows Azure CDN. We'll cover the differences in geographies (regions), what incurs cost, and some specialized billing cases.
What is a billing region?
A billing region is a geographic area used to determine what rate is charged for delivery of objects from the CDN. The current billing regions are:
Click here for more details.
How are delivery charges calculated by region?
The CDN billing region is based on the location of the source server delivering the content to the end user. The destination (physical location) of the client is not considered the billing region.
For example, if a user located in Mexico issues a request and this request is serviced by a server located in a US point of presence (for example Los Angeles) due to peering or traffic conditions, the billing region will be US.
What is a billable CDN transaction?
Any HTTP(S) request that terminates at the CDN is a billable event. This includes all response types, success, failure, or other. However, different responses may generate very different traffic amounts. For example, 304 NOT MODIFIED (and other header-only) responses generate very little transfer since they are a small header response; similarly, error responses (e.g., 404 NOT FOUND) are billable but incur very little cost because of the tiny response payload.
What other Windows Azure costs are associated with CDN use?
Using the Windows Azure CDN also incurs some usage charges on the services used as "origin" for your objects. These costs are typically a very small fraction of the overall CDN usage cost.
If you are using blob storage as "origin" for your content, you also incur charges for cache fills for:
If you are using "hosted service delivery" (available as of SDK 1.4) you will incur:
If your client uses byte-range requests (regardless of "origin" service):
How much transfer is incurred to support the cache?
How do I manage my costs most effectively?
Set the longest TTLs possible. Click here to learn more.