Designing Data Storage Architecture - Pricing Overview

本文详细介绍了Windows Azure的定价和计费方式,包括计算时间、数据库、虚拟机器、存储、数据传输和内容交付网络等内容的费用计算。
摘要由CSDN通过智能技术生成

https://www.windowsazure.com/en-us/pricing/details/

Learn more about Windows Azure pricing and billing meters.

Compute time, measured in service hours:

Price

Windows Azure compute hours are charged only when your application is deployed. When developing and testing your application, developers will want to remove the compute instances that are not being used to minimize compute hour billingPartial compute hours are billed as full hoursMore about Compute

The table below summarizes the Pay-As-You-Go price and the resources provided for each instance size.

Virtual Machine SizeCPU CoresMemoryCost Per Hour
Extra SmallShared768 MB$0.04
Small11.75 GB$0.12
Medium23.5 GB$0.24
Large47 GB$0.48
Extra Large814 GB$0.96

Details on the Virtual machine sizes can be found here

Billing Details

Billing meter for Windows Azure Compute is Compute Hour, and it is charged only when your application is deployed. When developing and testing your application, you should remove the compute instances that are not being used to minimize compute hour billing.

All compute hours are converted into small instance hours when presented on your bill. For example, one clock hour of a medium compute instance would be presented as two small compute instance hours at the small instance rate of $0.12 per hour on your bill. This table describes how each of the compute instance sizes is converted to the number of small compute instance hours:

Compute Instance SizeClock HoursSmall Instance Hours
Extra Small1 hour1/3 hour
Small1 hour1 hour
Medium1 hour2 hours
Large1 hour4 hours
Extra Large1 hour8 hours

Compute hours are billed based on the number of clock hours your service was deployed multiplied by the number of equivalent small compute instances included in your deployment. Partial compute instance hours (prior to conversion) are billed as full compute hours for each clock hour an instance is deployed. For example, if you deploy a small compute instance at 10:50 AM and delete the deployment at 11:10 AM, you will be billed fortwo small compute hours, one hour for usage during 10:50 AM to 11:00 AM and another hour for usage during 11:00 AM to 11:10 AM.

For other compute instance sizes you deploy, your hours will be converted into the equivalent small instance hours by multiplying by 1/3, 2, 4 or 8, depending on the compute instance size deployed. In addition, each time you delete your deployment and redeploy your service, you will be billed a minimum of one clock hour for each compute instance deployed. However, any instances deployed for less than five minutes within one clock hour will not be charged.

Learn more about compute.

Return to Top

Database, based on size of the database:

Price

SQL Azure Database is billed based on the size of the database, and it is available in two editions: Web and Business. The Web Edition and Business Edition SQL Azure databases provide up to 5 GB and 150 GB of a T-SQL based relational database, respectively.

Database

Standard pay-as-you-go pricing

Web Edition (up to 5 GB)

$9.99 per 1 GB of database per month

Business Edition (up to 150 GB)

$99.99 per 10 GB of database per month

(Maximum charge of $499.95 per database)*

*This maximum amount is calculated based on the accumulated charges for each database you deploy over the entire billing month.

Billing Details

We charge a monthly fee for each SQL Azure database, but we amortize that database fee over the month and calculate your fee on a daily basis. This daily fee is dependent on the database type (e.g., 1 GB Web Edition, 10 GB Business Edition, etc.), peak database size rolled up to the next billing increment, and number of databases you use. For example, if you utilized three 10 GB Business Edition databases for 1 day during a billing month, your daily usage for that day would show a little less than 0.1 10 GB Business Edition database (3 databases / 31 days).

All usage for each Web Edition database is converted into the 1 GB size and all usage for each Business Edition database is converted into the 10 GB size, rounded up to the next discrete billing increment. For example, if the peak size of your Business Edition database was 45 GB for a particular day, your usage for determining your charges would be considered 50 GB for that database for that day.

More about Databases   Return to Top

Virtual Machines:

Price

The pricing model for the Virtual Machine role is the same as that for the compute roles above. Customers are charged at an hourly rate depending on the compute instance size. The Windows Azure fee for running the VM role - whether consumption or commitment based - includes Windows Server licensing costs.

More about Virtual Machines

Return to Top

Storage, measured in GB:

Price

Storage is billed in units of the average daily amount of data stored (in GB) over a monthly period. For example, if you consistently utilized 10 GB of storage for the first half of the month and none for the second half of the month, you would be billed for your average usage of 5 GB of storage.

For Windows Azure Drive storage, you will be billed only for the storage space used by the page blob and the read/write transactions to the page blob. You will not be charged for read transactions that utilize the local drive cache. Windows Azure Drive usage is billed at the same rates as standard Windows Azure Storage and is included in these totals on your bill. There will not be a separate line item for Windows Azure Drive on your bill. Windows Azure Drive storage is currently in its beta release and a service level agreement is offered for this service.

Standard pay-as-you-go pricing for storage
$0.14 per GB stored per month based on the daily average
$0.01 per 10,000 storage transactions

More about Storage

Return to Top

Data transfers measured in GB (transmissions to and from the Windows Azure datacenter): All inbound data transfers are at no charge.

Price

All inbound data transfers, i.e. data going into the Window Azure platform datacenters, are free. Price for outbound data transfers, i.e. data going out of the Windows Azure platform datacenters, is shown below.

Pricing details for outbound data transfers
North America and Europe regions: $0.12
Asia Pacific Region: $0.19

Billing Details

Data transfers are charged based on the total amount of data moving in and out of the Windows Azure platform datacenters via the internet in a given billing period. Data transfers between Windows Azure services located within the same sub-region are not subject to charge. Data transfers between sub-regions are charged at normal rates on both sides of the transfer. A sub-region is the lowest level geo-location that you may select to deploy your applications and associated data. Below is a list of our regions and sub-regions for normal data transfer (except for CDN).

RegionsSub Regions
Zone 1North Europe
Western Europe
North Central US
Zone 2South Central US
East Asia
Southeast Asia
Return to Top

Content Delivery Network:

Price

CDN charges are incurred for the data requests the CDN receives and for the data it transfers out to satisfy these requests.

Standard pay-as-you-go monthly pricing for the CDN
$0.12per GB for data transfers from European and North American locations
$0.19 per GB for data transfers from other locations
$0.01 per 10,000 transactions

Billing Details

CDN charges shown above do not include charges associated with transferring this data from Windows Azure Storage to CDN. Any data transfers and storage transactions incurred to get data from Windows Azure Storage to the CDN will be charged separately at our normal Data Transfer and Storage transaction rates.

Windows Azure CDN data transfer charges are based on the data center location from where the traffic was served, not the end user's location. Below is a table that maps the data center locations to the appropriate zone for which they belong for billing purposes.

Billing RegionsGeographic Location
Zone 1North America
Europe
Zone 2Asia Pacific
Latin America
Middle East / Africa

Developers cannot control which locations are used to deliver content, so bills may reflect delivery charges from any of the Windows Azure CDN billing regions. User requests are directed to CDN nodes based on their Internet service provider's routing tables as well as network conditions. Users may be routed to locations that are preferred by their ISP, and/or nodes that are judged as "closer" in a logical sense, not necessarily physical proximity. For example, if a developer deploys content on the CDN and end users are in both Europe and Asia Pacific, the developer would likely see charges for delivery in both Zone 1 and Zone 2. However, some users may be served from one of our other geographic locations such as North America, based on routing tables and network status, if for example an Asia Pacific CDN node became unreachable. In this example, the developer would be charged for data transfers at Zone 1 rates for those users.

When the Windows Azure CDN receives a request for an object it does not have at an edge location, it will make a standard request of Windows Azure Storage to obtain the data. CDN charges do not include fees associated with transferring this data from Windows Azure Storage to CDN. Any data transfers and storage transactions incurred to get data from Windows Azure Storage to CDN will be charged separately at our normal Windows Azure Storage rates. CDN charges are incurred for data requests it receives and for the data it transfers out to satisfy these requests.

Availability of content in the Windows Azure CDN's local caches (often called "cache efficacy" or "offload") is nondeterministic but is influenced by multiple factors including:

  • Expiration ("max-age") header values
  • Overall total size of the developer's content library (how much could be cached)
  • Active working set (how much is currently cached)
  • Traffic (how much is being served)
  • Cache churn (how often are objects being added to cache, or aging out)

For example, a developer with a large ("wide") library with high churn and high traffic will have less cache efficacy than other users, because cache turnover is higher, so objects will be swapped in and out more frequently. This developer's overall Windows Azure Storage data transfer charges will be proportionally higher, since more origin requests are required. The overall end-user experience in this example will also be slightly slower on average since fewer requests are served from cache. The main cost control for developers to affect cache efficacy is the "max-age" HTTP header. Longer max-age headers allow the CDN to hold objects longer, reducing the need to make origin requests.

More about CDN

Return to Top

Caching, based on cache size per month:

Price

Caching is priced per cache size per month, no matter how much cache you actually end up using. In addition to the prices noted above for Caching, you will also be charged for the associated data transfers, for ingress and egress outside the data center that your app is provisioned.

Standard pay-as-you-go pricing for caching
128 MB cache for $45.00
256 MB cache for $55.00
512 MB cache for $75.00
1 GB cache for $110.00
2 GB cache for $180.00
4 GB cache for $325.00

Billing Details

Once you provision a cache of a certain size, the service limits the amount of data you put in the cache to that size. Your application might temporarily have more data in the cache than the size for which you signed up, but the system will soon take corrective action and delete data from your cache to keep your cache size within the provisioned size.

In order to make sure there is fair usage of resources, the service might enforce limitations based on the number of transactions being made against the cache, the total data transfer being consumed, or the number of concurrent connections being used. If you exceed the limitations enforced by the service, your application will be notified by receiving an exception specifying the specific quota limit you have reached.

The table below provides general guideline that can help you plan your usage of the service. This guideline is a high-level estimate and is subject to revision in the future.

Cache SizeTransactions Per HourData Transfers Per Hour (MB)Concurrent Connections
128MB400,0001,40010
256MB800,0002,80010
512MB1,600,0005,60020
1GB3,200,00011,20040
2GB6,400,00022,40080
4GB12,800,00044,800160

More about Caching

Return to Top

Virtual Network:

Windows Azure Connect and Windows Azure Traffic Manager are currently in CTP and available at no charge.More about Virtual Network

Return to Top

Service Bus:

Price

Effective December 10, 2011, Service Bus will be offered at no charge (except for standard data transfer fees). This promotional period will end for all billing months beginning after March 31, 2012. Service Bus will then be charged at the following rates noted below:

  • $0.01 per 10,000 messages
  • $0.10 per 100 relay hours (this only applies when using the Service Bus Relay capability)

Billing Details

Messages are charged based on the number of messages sent to, or delivered by, the Service Bus during the billing month. This includes delivery of “null” messages in response to receive requests against empty queues/subscriptions. Messages over 64KB in size will be charged an additional message for each additional 64KB of data (rounded up).

Relay hours will be charged from the time of creation to deletion (from when the first listener opens to when the last listener closes on the endpoint) and rounded up to the next whole hour. There is no relay hour charge if you are only using Service Bus Queues and Topics.

In addition to the prices noted above for Service Bus, you will also be charged for the associated data transfers for egress outside the data center that your app is provisioned in.

More about Service Bus

Return to Top

Access Control:

Price

For AppFabric Access Control transactions, customers will be charged the actual number of transactions utilized for the billing period (i.e., not in discrete blocks of 100,000 transactions), plus data transfers in or out. More about Access Control

Standard pay-as-you-go pricing for Access Control
$1.99 per 100,000 transactions*

*We currently are running a promotion and will not charge for the Access Control service until December 1, 2012.

### 回答1: 《Designing Data-Intensive Applications》这本书是一本关于设计和构建大型数据应用程序的指南。它重点关注数据存储、处理和传输方面的现代技术。这本书由三部分组成:第一部分围绕着数据存储系统展开,包括传统的关系型数据库和现代的NoSQL数据库等;第二部分则聚焦于数据处理,涵盖流处理、批处理和交互式查询等领域;第三部分则探讨了如何构建可靠、可扩展且具有良好性能的分布式系统。无论是新手还是老手,都可以从本书中获得一些有价值的见解。这本书概述了不同技术在数据处理方面的优缺点,并介绍了一些构建大型、高效数据应用程序的最佳实践。另外,由于该书旨在让读者获得对现代架构和技术的深刻理解,因此它也介绍了一些分布式系统的核心理论,例如CAP定理和BASE原则等。这本书的读者包括数据科学家、软件工程师、数据工程师和系统管理员。总之,如果你正在构建一个数据密集型应用程序,想要了解最新的技术和最佳实践,那么《Designing Data-Intensive Applications》绝对值得一读。 ### 回答2: 《设计数据密集型应用程序》(Designing Data-Intensive Applications)是一本由 Martin Kleppmann 所著的计算机科学类图书,这本书讨论了当今主要的数据系统和应用程序所面临的问题和挑战,并提供了一些解决方案。这本书内容涵盖了分布式系统、数据存储和查询、数据一致性与容错性、流处理、数据流水线、实时分析等领域,不仅提供了丰富的理论知识,还有很多实践案例和相关技术细节。 对于软件工程师、架构师、数据工程师等人来说,这本书是一本非常重要的访问。如果你正在开发一个数据密集型的应用或系统,这本书提供了很多有用的指导和建议。例如,这本书会告诉你如何选择和使用不同的数据存储技术,如何设计高效的数据处理流水线,如何保证系统的可扩展性和容错性等等。 《设计数据密集型应用程序》还使用了很多实用的案例和场景,比如 Twitter 的分布式消息队列 Kafka,Google 的基于 Paxos 算法的分布式一致性协议 Chubby,Facebook 的实时数据处理系统 Apache Samza 等等。通过这些案例,读者可以更好地了解如何应用书中的理论知识到实际工作中。 总之,《设计数据密集型应用程序》是一本值得阅读的计算机科学类图书,无论你是软件工程师、数据工程师、系统架构师等,都有望从中获得很多启发。 ### 回答3: Designing Data-Intensive Applications是一本讲述大数据应用程序设计的书籍。这本书主要涵盖了数据密集型应用程序设计的方方面面,包括数据存储和查询、数据处理和流处理、分布式系统和高可用性、性能和可扩展性等。它通过介绍各种不同的数据管理工具和技术,帮助读者了解如何在大数据领域中设计出高效和可靠的应用程序。 在设计数据密集型应用程序时,需要考虑很多因素。从数据存储和查询的角度来看,我们需要考虑使用哪种数据库或数据存储方案,并且了解其适用的场景和可扩展性。同时还需要思考如何使用数据查询工具来优化查询性能。 在数据处理和流处理方面,我们需要选择正确的数据处理框架和工具,以处理大数据集合。我们也需要了解如何设计分布式系统,并且使其具有高可用性和容错性。性能和可扩展性也是设计数据密集型应用程序时的至关重要因素,因此我们需要考虑如何优化系统吞吐量和处理能力,并在需要时进行水平扩展。 总之,Designing Data-Intensive Applications是一本非常有价值的书籍,可以帮助读者了解如何在大数据领域中进行应用程序设计。它提供了丰富的知识和有实际应用的案例,让读者在实践中掌握数据密集型应用程序设计的关键技能。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值