DataWorks:Billing for legacy resource groups

Features

Exclusive data integration resource groups provide the following features:

• Support data synchronization in complex network environments, such as cross-cloud environments (Finance Cloud, China Gov Cloud), cross-Alibaba Cloud accounts, and on-premises IDC data synchronization.

• Provide extensive product capabilities:

  • Support batch data synchronization, such as incremental and full data synchronization and single-table or sharded data synchronization. For more information, see Overview of batch synchronization.

  • Support real-time data synchronization, such as single-table real-time synchronization and full-database real-time synchronization. For more information, see Overview of the real-time synchronization feature.

  • Provide full and incremental synchronization tasks between various data sources, such as full-database batch synchronization and single-table or full-database real-time synchronization. For more information, see Overview of the full and incremental synchronization feature.

Limits

The following limits apply to exclusive data integration resource groups:

• Resource groups cannot be deleted or released before they expire. After expiration, services are suspended and resources are released based on the specified schedule.

• Cross-region usage is not supported. For example, an exclusive data integration resource group in the China (Shanghai) region can only be used for workspaces in the China (Shanghai) region.

• Access to the Alibaba Cloud classic network is not supported. If your data source is in a classic network environment, we recommend that you migrate it to a VPC.

Billing

• Performance metrics

  Specification	Maximum concurrent threads for batch synchronization
  4c8g	8
  8c16g	16
  12c24g	24
  16c32g	32
  24c48g	48

  Specification	Recommended resource specification per task
  MySQL source real-time sync, 1 database	4c8g
  MySQL source real-time sync, 2-5 databases	8c16g
  MySQL source real-time sync, 6+ databases	12c24g
  PolarDB-X source real-time sync	12c24g
  Kafka source real-time sync	4c8g
  Other single-table real-time tasks	4c8g

• Pricing

  Pricing by region (click to expand)

  Region	Exclusive data integration resource group specification	Unit price (USD/month)
  China (Hangzhou)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Shanghai)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Shenzhen)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Beijing)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Zhangjiakou)	4c8g	57.27
  	8c16g	114.34
  	12c24g	171.61
  	16c32g	228.68
  	24c48g	343.02
  China (Chengdu)	4c8g	62.49
  	8c16g	124.79
  	12c24g	187.09
  	16c32g	249.38
  	24c48g	374.17
  US (Silicon Valley)	4c8g	149.26
  	8c16g	298.53
  	12c24g	447.77
  	16c32g	597.06
  	24c48g	895.55
  US (Virginia)	4c8g	110.63
  	8c16g	221.26
  	12c24g	331.89
  	16c32g	442.53
  	24c48g	663.78
  China (Hong Kong)	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	832.35
  Singapore	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	832.35
  Australia (Sydney)	4c8g	147.51
  	8c16g	295.02
  	12c24g	442.52
  	16c32g	590.03
  	24c48g	885.03
  Germany (Frankfurt)	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	817.91
  Malaysia (Kuala Lumpur)	4c8g	130.01
  	8c16g	259.06
  	12c24g	390.04
  	16c32g	517.92
  	24c48g	780.07
  Indonesia (Jakarta)	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	832.35
  India (Mumbai) Being discontinued	4c8g	115.89
  	8c16g	231.00
  	12c24g	347.86
  	16c32g	462.20
  	24c48g	695.72
  Japan (Tokyo)	4c8g	158.92
  	8c16g	316.97
  	12c24g	474.14
  	16c32g	633.94
  	24c48g	948.27
  UK (London)	4c8g	104.67
  	8c16g	209.33
  	12c24g	314.00
  	16c32g	418.67
  	24c48g	628.00
  UAE (Dubai)	4c8g	166.38
  	8c16g	331.80
  	12c24g	498.38
  	16c32g	663.80
  	24c48g	996.76

Specification selection and cost estimation

You can use the Exclusive Resource Group Calculator to estimate the required specifications and costs. When estimating specifications and costs, you can go to the Operation Center in DataWorks and check the Overview to view the number of running instances and concurrency as a reference for estimation.

Use exclusive data integration resource groups

Manage exclusive data integration resource groups

• Scale-out and scale-in: If the machine specification or quantity of the purchased resource group does not meet your actual needs, you can scale out or scale in the resource group as needed. For more information, see Scaling.

  Note

  Scale-out requires payment of the price difference for the additional resources from the time the scale-out takes effect to the original order expiration time. For scale-in, DataWorks refunds the price difference from the time the scale-in takes effect to the original order expiration time.

• Specification change (upgrade or downgrade): If the purchased resource group specification does not meet your actual needs, you can change the specification as needed. For more information, see Change specifications.

  Note

  • When you change the resource group specification, the specifications of all machines in the resource group are changed uniformly

  • Upgrading requires payment of the price difference for resources from the current time to the original order expiration time. For downgrading, DataWorks refunds the price difference from the time the downgrade takes effect to the original order expiration time.

• Expiration and renewal: If a resource group is about to expire, you can renew it. If you do not renew, the resource group will be suspended or released after expiration. For more information, see Expiration and renewal.

• View bills: You can view bills to understand the details of each billable item. For more information, see View bill details.

FAQ

For frequently asked questions about exclusive resource groups, see Exclusive resource groups.

Billing

• Billing scope

  The number of successfully run instances generated by data integration tasks running as periodic instances, backfill instances, manual instances, DataStudio workflow runs, or smoke tests are all included in the billing scope. The platform charges based on the total number of successfully run data integration task instances per day.

  Note

  • Number of successfully run data integration task instances = Data integration task concurrency x Number of scheduling instances

  • Running data integration task instances on shared data integration (testing) resource groups also consumes resources of shared scheduling resource groups.

  • The maximum number of instances that can run per day is 120,000. Instances exceeding this limit cannot be scheduled normally. If your actual workload exceeds this limit, submit a ticket for consultation.

  • Instances that run on exclusive data integration resource groups are not counted toward the shared data integration (testing) resource group quota.

• Pricing

  DataWorks uses a 6-tier pricing model and charges daily based on the tier that corresponds to the number of successfully run data integration task instances per day.

  Pricing by region (click to expand)

  Region	Pricing tier	Billing cycle	Fee
  China (Hangzhou) China (Shanghai) China (Beijing) China (Shenzhen) China (Chengdu) China (Zhangjiakou) China (Hong Kong)	1-10 successful instances/day	Day	0.00 USD/day
  	11-500 successful instances/day	Day	0.15 USD/day
  	501-5,000 successful instances/day	Day	0.93 USD/day
  	5,001-20,000 successful instances/day	Day	3.10 USD/day
  	20,001-50,000 successful instances/day	Day	7.74 USD/day
  	50,001-120,000 successful instances/day	Day	15.48 USD/day
  Singapore Australia (Sydney) Malaysia (Kuala Lumpur) Indonesia (Jakarta) Japan (Tokyo) US (Silicon Valley) US (Virginia) Germany (Frankfurt) UK (London) UAE (Dubai)	1-10 successful instances/day	Day	0.00 USD/day
  	11-500 successful instances/day	Day	0.23 USD/day
  	501-5,000 successful instances/day	Day	1.39 USD/day
  	5,001-20,000 successful instances/day	Day	4.64 USD/day
  	20,001-50,000 successful instances/day	Day	11.61 USD/day
  	50,001-120,000 successful instances/day	Day	23.22 USD/day

Deductions and overdue payments

• Deduction rules

  The billing system settles the number of successfully run instances in the previous calendar day at 00:00 each day and deducts fees based on the price tier in the pricing standard. For more information, see Overdue payments。

  Example: A user configures two synchronization tasks A and B in a DataWorks workspace in the China (Shanghai) region, using shared data integration (testing) resource groups to run the tasks.

  • Task A: Concurrency is set to 2, scheduled daily, generating 1 scheduling instance per day.

  • Task B: Concurrency is set to 5, scheduled hourly, generating 24 scheduling instances per day.

  If all task instances run successfully, the daily fee is calculated as follows:

  1. Settlement of daily cumulative data integration task instances: 2 * 1 + 5 * 24 = 122.

  2. The daily data integration task instance count 122 falls in the 11-500 tier. Checking the price for this tier, the daily fee deducted is USD 0.15.

• Overdue payment rules

  If your account has an overdue payment, the platform will extend your service for 360 hours and send notifications reminding you to renew. If you do not top up in time, your service may be suspended. For more information, see Overdue payments.

• View bills: You can view bills to understand the details of each billable item. For more information, see View bill details.

FAQ

For frequently asked questions about shared data integration (testing) resource groups, see Shared resource group for Data Integration (debugging).

Applicable scenarios

Exclusive scheduling resource groups are applicable to the following scenarios:

• Tasks have high timeliness requirements, and you want to avoid task delays caused by resource contention on shared resource groups.

• You need to flexibly adjust the resource group size.

• You need to access public network addresses, VPCs, or IDCs.

• You need to perform access control through IP address whitelists.

• Applicable to task types that only support running on exclusive resource groups, such as EMR, CDH, and AnalyticDB for PostgreSQL.

Limits

The following limits apply to exclusive scheduling resource groups:

• Resource groups cannot be deleted or released before they expire. After expiration, services are suspended and resources are released based on the specified schedule.

• Cross-region usage is not supported. For example, an exclusive data integration resource group in the China (Shanghai) region can only be used for workspaces in the China (Shanghai) region.

• Running Yum commands is not supported.

Billing

• Performance metrics

  Specification	Maximum concurrent instances
  4c8g	16
  8c16g	32
  12c24g	48
  16c32g	64
  24c48g	96

• Pricing

  Pricing by region (click to expand)

  Region	Specification	Unit price (USD/month)
  China (Hangzhou)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Shanghai)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Shenzhen)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Beijing)	4c8g	76.23
  	8c16g	152.45
  	12c24g	228.68
  	16c32g	304.91
  	24c48g	457.36
  China (Zhangjiakou)	4c8g	57.27
  	8c16g	114.34
  	12c24g	171.61
  	16c32g	228.68
  	24c48g	343.02
  China (Chengdu)	4c8g	62.49
  	8c16g	124.79
  	12c24g	187.09
  	16c32g	249.38
  	24c48g	374.17
  US (Silicon Valley)	4c8g	149.26
  	8c16g	298.53
  	12c24g	447.77
  	16c32g	597.06
  	24c48g	895.55
  US (Virginia)	4c8g	110.63
  	8c16g	221.26
  	12c24g	331.89
  	16c32g	442.53
  	24c48g	663.78
  China (Hong Kong)	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	832.35
  Singapore	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	832.35
  Australia (Sydney)	4c8g	147.51
  	8c16g	295.02
  	12c24g	442.52
  	16c32g	590.03
  	24c48g	885.03
  Germany (Frankfurt)	4c8g	138.73
  	8c16g	276.58
  	12c24g	408.96
  	16c32g	553.16
  	24c48g	817.91
  Malaysia (Kuala Lumpur)	4c8g	130.01
  	8c16g	259.06
  	12c24g	390.05
  	16c32g	517.92
  	24c48g	780.07
  Indonesia (Jakarta)	4c8g	138.73
  	8c16g	276.58
  	12c24g	416.18
  	16c32g	553.16
  	24c48g	832.35
  India (Mumbai) Being discontinued	4c8g	115.89
  	8c16g	231.00
  	12c24g	347.86
  	16c32g	462.20
  	24c48g	695.72
  Japan (Tokyo)	4c8g	158.92
  	8c16g	316.97
  	12c24g	474.14
  	16c32g	633.94
  	24c48g	948.27
  UK (London)	4c8g	104.67
  	8c16g	209.33
  	12c24g	314.00
  	16c32g	418.67
  	24c48g	628.00
  UAE (Dubai)	4c8g	166.38
  	8c16g	331.80
  	12c24g	498.38
  	16c32g	663.80
  	24c48g	996.76

Specification selection and cost estimation

You can use the Exclusive Resource Group Calculator to estimate the required specifications and costs. When estimating specifications and costs, you can go to the Operation Center in DataWorks and check the Overview to view the number of running instances and concurrency as a reference for estimation.

Use exclusive scheduling resource groups

Manage exclusive scheduling resource groups

• Scale-out and scale-in: If the machine specification or quantity of the purchased resource group does not meet your actual needs, you can scale out or scale in the resource group as needed. For more information, see Scaling.

  Note

  Scale-out requires payment of the price difference for the additional resources from the time the scale-out takes effect to the original order expiration time. For scale-in, DataWorks refunds the price difference from the time the scale-in takes effect to the original order expiration time.

• Specification change (upgrade or downgrade): If the purchased resource group specification does not meet your actual needs, you can change the specification as needed. For more information, see Change specifications.

  Note

  • When you change the resource group specification, the specifications of all machines in the resource group are changed uniformly

  • Upgrading requires payment of the price difference for resources from the current time to the original order expiration time. For downgrading, DataWorks refunds the price difference from the time the downgrade takes effect to the original order expiration time.

• Expiration and renewal: If a resource group is about to expire, you can renew it. If you do not renew, the resource group will be suspended or released after expiration. For more information, see Expiration and renewal.

• View bills: You can view bills to understand the details of each billable item. For more information, see View bill details.

FAQ

For frequently asked questions about exclusive resource groups, see Exclusive resource groups.

Billing

• How fees are generated

  When tasks are scheduled at hourly or minute intervals, multiple hourly or minute instances are generated daily. Billing is based on the actual number of instances generated and successfully executed. You can go to Operation Center > Cycle Task O&M > Periodic Instances, on the Instance View tab, filter by shared scheduling resource group, and refer to the instance list on the page to estimate the number of instances generated by the workspace.

• Billing scope

  Shared scheduling resource groups are billed based on instances. DataWorks charges for instances when the following conditions are met:

  • Instances are submitted to the scheduling system:

    All types of instances generated by nodes submitted to the scheduling system (except instances generated by virtual nodes) are included in the billing scope, including periodic instances, manual instances, test instances, and backfill instances.

  • Instances run successfully:

    Only instances that show a Successful status on the Operation Center > Task O&M are included in the billing scope. Instances that have not run (instances already generated), frozen instances, and dry-run instances are not charged.

  Note

  The maximum number of instances that can run per day is 120,000. Instances exceeding this limit cannot be scheduled normally. If your actual workload exceeds this limit, submit a ticket for consultation.

• Pricing

  DataWorks uses a 12-tier pricing model and charges daily based on the tier that corresponds to the number of successfully run instances per day.

  Pricing by region (click to expand)

  Region	Pricing tier	Billing cycle	Fee
  China (Hangzhou) China (Shanghai) China (Beijing) China (Shenzhen) China (Chengdu) China (Zhangjiakou) China (Hong Kong)	1-10 successful instances/day	Day	0.00 USD/day
  	11-500 successful instances/day	Day	0.15 USD/day
  	501-5,000 successful instances/day	Day	9.29 USD/day
  	5,001-20,000 successful instances/day	Day	23.22 USD/day
  	20,001-50,000 successful instances/day	Day	41.79 USD/day
  	50,001-120,000 successful instances/day	Day	92.87 USD/day
  Singapore Australia (Sydney) Malaysia (Kuala Lumpur) Indonesia (Jakarta) Japan (Tokyo) US (Silicon Valley) US (Virginia) Germany (Frankfurt) UK (London) UAE (Dubai) India (Mumbai) Being discontinued	1-10 successful instances/day	Day	0.00 USD/day
  	11-500 successful instances/day	Day	0.23 USD/day
  	501-5,000 successful instances/day	Day	13.93 USD/day
  	5,001-20,000 successful instances/day	Day	34.82 USD/day
  	20,001-50,000 successful instances/day	Day	62.68 USD/day
  	50,001-120,000 successful instances/day	Day	139.30 USD/day

Deductions and overdue payments

• Deduction rules

  The billing system settles the number of successfully run instances in the previous calendar day at 00:00 each day and deducts fees based on the price tier in the pricing standard. For more information, see Overdue payments。

  Example: A user's DataWorks workspace is deployed in the China (Shanghai) region. On April 30, 2019, a total of 502 instances ran successfully. After May 1, 2019 00:00, a fee of USD 9.29 will be deducted.

• Overdue payment rules

  If your account has an overdue payment, the platform will extend your service for 360 hours and send notifications reminding you to renew. If you do not top up in time, your service may be suspended. For more information, see Overdue payments.

• View bills: You can view bills to understand the details of each billable item. For more information, see View bill details.

FAQ

• Question: How is the fee for a single instance calculated?

• Answer: Shared scheduling resource groups use pay-as-you-go billing and charge daily based on the tier that corresponds to the number of successfully run instances per day. The fee cannot be split to calculate the cost per instance, so bills cannot be queried by instance.

Applicable scenarios

Exclusive DataService resource groups are applicable to the following scenarios:

• You need to support high-frequency and high-concurrency calls to DataService APIs and require timely data results.

• You need to flexibly adjust the resource group size.

• You need to access data sources in public network, Alibaba Cloud VPC, or IDC network environments.

Limits

The following limits apply to exclusive DataService resource groups:

• Resource groups cannot be deleted or released before they expire. After expiration, services are suspended and resources are released based on the specified schedule.

• Only available in the China (Shanghai) and China (Hong Kong) regions.

Billing

• Performance metrics

  Resource group specification	Maximum requests per second (QPS)	Service availability (SLA)	Supported regions
  api.s1.small	500	99.95%	China (Shanghai) China (Hong Kong)
  api.s1.medium	1000	99.95%
  api.s1.large	2000	99.95%

  Note

  Maximum requests per second (QPS): The QPS threshold of a resource group is calculated based on actual business scenarios. You can refer to the following information to estimate the QPS threshold.

  • Whether the API is generated in script mode.

  • Whether the API has the result pagination feature enabled.

  • The average execution time of the SQL configured in the API on the data source is 100 milliseconds.

  • The average size of data returned per API call is 3,000 bytes.

  If your actual business scenario differs significantly from the above data, join the DataWorks DingTalk group to consult technical support. We will recommend appropriate resource group specifications based on your actual business scenario.

• Pricing

  Pricing by region (click to expand)

  Region	Exclusive DataService resource group specification	Unit price (USD/month)
  China (Shanghai)	api.s1.small	325.3
  	api.s1.medium	650.6
  	api.s1.large	1301.2
  China (Hong Kong)	api.s1.small	953.00
  	api.s1.medium	1906.00
  	api.s1.large	3813.00

Use exclusive DataService resource groups

Manage exclusive DataService resource groups

• Upgrade: If the purchased resource group specification does not meet your actual needs, you can upgrade the configuration as needed. For more information, see Change specifications.

  Note

  • Upgrading only upgrades the resource specification of the purchased order without increasing the number of resource groups, and you must pay the price difference from the current time to the original order expiration time.

  • After the upgrade is performed, the new configuration takes effect within 10 minutes after the upgrade order is paid.

• Expiration and renewal: If a resource group is about to expire, you can renew it. If you do not renew, the resource group will be suspended or released after expiration. For more information, see Expiration and renewal.

• View bills: You can view bills to understand the details of each billable item. For more information, see View bill details.

Billing

• Fee composition

  DataService fees consist of call count and execution time. Only valid calls to DataService APIs are billed (including online test calls on the DataService page).

  • Valid calls: After a call request is executed, the response errCode is 0.

  • Invalid calls: After a call request is executed, the response errCode is not 0.

• Free tier description

  The platform provides a free tier for each Alibaba Cloud primary account each month. RAM users share the free tier with the primary account. No fees are charged within the free tier.

  • Call count: The first 1 million calls per user per month are free.

  • Execution time: The first 400,000 GB*s of execution per user per month is free.

  Note

  The free tier resets at the beginning of each calendar month and does not accumulate across months.

• Pricing

  Fees are charged for usage that exceeds the free tier.

  Pricing by region (click to expand)

  Billable item	Unit	Unit price	Remarks
  API calls	per million calls	0.21 USD/million calls	N/A
  Execution time	Memory*seconds (GB*s)	0.000017193 USD/GB*s	The minimum time unit is 100 ms. Usage less than 100 ms is rounded up to 100 ms.

  Fee calculation example

  For example, this month you called APIs 10 million times, with each API allocated 2 GB of memory and running for 1,060 ms (billed as 1.1 seconds), the fees you need to pay are as follows:

  • Monthly call count and fee

    • Billable calls: There is a free tier of 1 million calls per month, so the billable calls for this month are 10,000,000 - 1,000,000 = 9,000,000.

    • Call fee: The price per 1 million calls is USD 0.21, so the total call fee for this month is 900 / 100 * 0.21 = USD 1.89.

  • Monthly execution time and fee

    Note

    The measurement unit for execution time is memory (GB) * seconds, i.e., GB*s. The minimum time unit is 100 ms. Usage less than 100 ms is rounded up to 100 ms. Therefore, the execution time in this example of 1,060 ms is calculated as 1.1 s.

    • Billable execution time: Total execution time = Number of calls x Memory consumed per call (GB) x Runtime per call (seconds), which is 10,000,000 * 2 * 1.1 = 22,000,000 GB*s. There is a free tier of 400,000 GB*s of execution time per month, so the actual billable execution time is 22,000,000 - 400,000 = 21,600,000 GB*s.

    • Execution time fee: The price per GB*s is USD 0.000017193, so the total execution time fee for this month is 21,600,000 * 0.000017193 = USD 371.37.

  • Monthly total fee

    Monthly total fee = Monthly call fee + Monthly execution time fee, which is 1.89 + 371.37 = USD 373.26.

Deductions and overdue payments

• Deduction rules

  The billing system calculates the fees consumed in the previous hour at the beginning of each hour, generates a bill, and deducts the actual amount from the Alibaba Cloud primary account balance.

• Overdue payment rules

  If your account has an overdue payment, the platform will extend your service for 360 hours and send notifications reminding you to renew. If you do not top up in time, your service may be suspended. For more information, see Overdue payments.

• View bills: You can view bills to understand the details of each billable item. For more information, see View bill details.