Astra DB Provisioned Capacity Consumption Model
Provisioned Capacity is an alternative Enterprise consumption model to On Demand but based on the same serverless architecture. There are a number of factors that a larger Enterprise should consider when deciding between On Demand and Provisioned Capacity.
Performance Needs
The reality of any serverless architecture is that it takes time to scale to meet demand and as any system scales there will be an impact on performance. For some customers their preference is to have an ‘always on’ capacity available that can deal with sudden changes in needs without the need to auto-scale. We can support that through Provisioned Capacity which allows you to have an ‘always on’ base capacity available to you. This is typically used for customers with strict performance requirements but workloads that have intra-day volatility, low throughput combined with low latency requirements or batch workloads.
Committed Capacity
As outlined above, mature workloads often have a base ‘always on’ need and scale to zero is not a requirement. For those workloads, we’re also able to offer preferential rates for a longer term commitment to a given capacity. Provisioned Capacity Reserved Capacity Units are an annual commitment to a fixed capacity that is billed regardless of actual usage. This is typically a good fit for customers that have a workload with a base capacity that they can commit to for an extended period.
Peak or Seasonal Needs
Building on the committed capacity above, some workloads may fit the criteria for a Committed Capacity for most of the year but have periods when additional capacity is needed e.g. peak or seasonal needs. For those workloads, you can combine Reserved Capacity Units for the long term base capacity with Hourly Capacity Units which only need a minimum of 24 hours commitment. This allows you to take advantage of the preferential rates available for Reserved Capacity with the flexibility of a shorter term commitment for peak or seasonal needs.
You can see more details on the rates for Reserved and Hourly Capacity Units in the Metering Details section below.
Metering Unit Rates
AWS
Standard Region | Premium Region | |
---|---|---|
Reserved Capacity Units (hourly) | 4.9500 | - |
Hourly Capacity Units | 7.4300 | - |
Data Storage (GB/month) | 0.2500 | - |
Data Transfer - Same Region (GB) | 0.0200 | - |
Data Transfer - Within Cloud Provider Network (GB) | 0.0500 | - |
Data Transfer - Internet (GB) | 0.1100 | - |
Optional Add-Ons | ||
Private Endpoint ($0.01/hr and data transfer charge of $0.01/GB ingress and egress) | ||
Dedicated Reserved Capacity Units (hourly) | 5.9400 | - |
Dedicated Hourly Capacity Units | 8.9100 | - |
Dedicated Capacity Region (hourly) | 17.1200 | - |
Cache Optimized Reserved CU Add-on (hourly) | 1.6300 | - |
Cache Optimized Hourly CU Add-on | 2.4500 | - |
Cache Optimized Dedicated Reserved CU Add-on (hourly) | 1.9600 | - |
Cache Optimized Dedicated Hourly CU Add-on | 2.9400 | - |
Metering Details
Usage | Billing Unit | Metering Details |
---|---|---|
Reserved Capacity Unit | A Provisioned Capacity “Reserved Capacity Unit” (RCU) is the smallest deployment unit of Serverless Capacity (includes 3 replicas). Pricing is based on an hourly rate and is committed for a one year term. | Reserved Capacity Units are available, committed and billed 24 x 7 for a one year term, commencing when the RCU is created. |
Hourly Capacity Units | A “Hourly Capacity Unit” (HCU) is the smallest deployment unit of Serverless Capacity (includes 3 replicas). It is priced on a per hour basis on a non-committed basis. | Hourly Capacity Units are charged in one hour increments for any hour in which database read or write operations are performed. If a customer allows auto-scaling, it is the amount in excess of any Reserved Capacity Units required to support a customer’s operations. |
Storage | “Data Storage” means all data stored into the Database including the data, indexes and metadata. | Storage is calculated based on logical storage consumption. Data Storage is measured in GB per month, using the maximum data stored in the given month for the usage calculation. You are not billed extra for standard backups of your data (it is included in the base storage costs). |
Data Transfer | “Data Transfer” means the transfer of Customer Data out of the database. Billable units and pricing vary depending on whether the Data Transfer occurs within the same region of a cloud provider network (“Data Transfer - Same Region”), across regions within the same cloud provider network (“Data Transfer - Cross Region within Cloud Provider Network”), or leaves the cloud provider network over the internet (“Data Transfer - Internet”). | Data Transfer charges are measured in GB. |
Optional Features | Description | Metering Details |
---|---|---|
Cache Optimized Capacity Units | “Cache Optimized Capacity Units (CU’s)” provide additional RAM/Local disk than the Capacity Units outlined above. | The referenced price is incremental to the pricing for 1) Reserved Capacity Units, 2) Hourly Capacity Units, 3) Dedicated Reserved Capacity Units and 4) Dedicated Hourly Capacity Units. Reserved Capacity Units are available, committed and billed 24 x 7 for the contract term regardless of activity once deployed. |
Private Endpoint | Creating a “Private Endpoint” allows users to securely connect applications and third party SaaS offerings to Astra DB. | Users are billed at a fixed rate per hour plus data transfer charges per GB. Data transfer charges using private endpoints are for the transfer of Customer Data into and out of the database. Cloud providers will also bill for use of private endpoint capabilities. |
Dedicated Reserved Capacity Units | “Dedicated Reserved Capacity Units” provide single tenant customer capacity. Pricing is based on an hourly rate and is committed for a one year term. | Dedicated Reserved Capacity Units are available, committed and billed 24 x 7 for a one year term, commencing when the dedicated RCU is created. |
Dedicated Hourly Capacity Units | “Dedicated Hourly Capacity Units” provide single tenant customer capacity. Non-dedicated hourly capacity units may be multi-tenant. | Hourly Capacity Units are charged in one hour increments for any hour in which database read or write operations are performed. If a customer allows auto-scaling, it is the amount in excess of any Reserved Capacity Units required to support a customer’s operations. |
Dedicated Capacity Region | “Dedicated Capacity Region” provides customer isolation at the cloud provider region level for all databases within that region. | Dedicated Capacity Region requires an annual commitment, but credits are consumed on an hourly basis over the year. Only one dedicated private network is required per cloud provider region. |
Have a Question?
Please Contact Your Account Manager with QuestionsPricing is subject to change and may be updated on this page. When Provisioned Capacity Units are available to deploy and managed within the Astra Dashboard, pricing within the Astra Dashboard will supersede any pricing information on this page.