All Products
Search
Document Center

DataWorks:Billing of data synchronization

Last Updated:Sep 26, 2024

When you use DataWorks to run data synchronization tasks, DataWorks charges you for the data synchronization tasks based on the type of the resource group that you use. This topic describes the billing details of data synchronization tasks that are run on different types of resource groups.

Fee generation scenarios

You are charged if you run the following types of data synchronization tasks in different modules:

For more information about the types of data synchronization tasks supported by DataWorks, see the Appendix: Types of data synchronization tasks section in this topic.

Precautions

This topic describes only the billing of data synchronization. If data synchronization tasks need to be deployed to the production environment for periodic scheduling, you will also be charged for task scheduling. For more information, see Billing of task scheduling.

Resource group type selection

The following table describes the types of resource groups that you can use to run data synchronization tasks.

Resource group type

Description

Billing references

Serverless resource group (recommended)

This type of resource group is exclusively used by each tenant. You can use one serverless resource group to complete operations such as data synchronization, task scheduling, and debugging and calling of DataService Studio APIs. You no longer need to separately purchase and configure resource groups for different scenarios.

Billing of serverless resource groups (recommended)

Old-version resource group

Exclusive resource group for Data Integration:

This type of resource group is exclusively used by each tenant and can be used to run only data synchronization tasks. If a large number of data synchronization tasks need to be run in parallel, you can use exclusive resource groups for Data Integration to ensure fast and reliable data transmission.

Billing of old-version resource groups

Compared with an old-version resource group, a serverless resource group can be used in different modules. This reduces the waste of resource fragments. We recommend that you use serverless resource groups. For more information about the comparison between old-version and serverless resource groups, see Billing of serverless resource groups.

Billing of serverless resource groups (recommended)

You are charged for serverless resource groups based on the number of CUs. One CU equals 1 vCPU core and 4 GiB of memory. The following content describes the billing details when you use a serverless resource group to run data synchronization tasks:

  • If you use the pay-as-you-go billing method, you are charged based on the number of CUs that are actually used to run tasks. For more information, see the Pay-as-you-go serverless resource group section of the "Billing of serverless resource groups" topic.

  • If you use the subscription billing method, you are charged based on the number of CUs that you purchase and the number of months of your subscription duration. For more information, see the Subscription serverless resource group section of the "Billing of serverless resource groups" topic.

Note

If you run a data synchronization task over the Internet, the Internet traffic fee that is generated is not included in your DataWorks bill.

Billing of old-version resource groups

If you use an exclusive resource group for Data Integration, you are charged based on the specifications of the resource group, such as the 4c8g specifications. For more information, see Billing of exclusive resource groups for Data Integration (subscription).

If you run a data synchronization task over the Internet, the Internet traffic fee that is generated is included in your DataWorks bill. For more information, see Billing of Internet traffic.

Appendix: Types of data synchronization tasks

DataWorks supports various synchronization scenarios, including batch synchronization, real-time synchronization, and synchronization of full data in batches and incremental data in real time. You can synchronize data between heterogeneous data sources in complex scenarios.

Each time you use a serverless resource group to run a type of data synchronization task, a default number of available CUs are allocated to this type of data synchronization task. If the default number does not meet your business requirements, you can adjust the number based on your business requirements. The following table describes the types of data synchronization tasks and the default number of CUs that can be allocated to each type of data synchronization task.

Task type

Default number of CUs allocated

Modifiable

Batch synchronization

0.5

Yes

Real-time synchronization

2

Yes

References