Exclusive resource groups for Data Integration provide dedicated computing resources to ensure fast and stable data transmission when Data Integration tasks require high concurrency and cannot be staggered. This topic provides an overview of exclusive resource groups for Data Integration.
DataWorks no longer recommends exclusive resource groups for Data Integration
DataWorks no longer recommends exclusive resource groups for Data Integration. We recommend that you use serverless resource groups. A serverless resource group covers the core capabilities of legacy resource groups (exclusive resource groups for scheduling, exclusive resource groups for Data Integration, exclusive resource groups for Data Service, and shared resource groups). A single serverless resource group can handle data synchronization, task scheduling and execution, and API operation calls and management.
Capabilities
Exclusive resource groups for Data Integration support:
Data synchronization in complex network environments, including cross-cloud platforms (such as Alibaba Finance Cloud and Alibaba Gov Cloud), across different Alibaba Cloud accounts, and with on-premises data centers.
Rich product capabilities: Data Integration provides high-speed and stable data movement and synchronization across heterogeneous data sources, supporting batch and real-time synchronization, single-table and full-database synchronization, and full and incremental synchronization. For more information, see Supported data sources and synchronization solutions.
Exclusive resource groups for Data Integration guarantee the total number of concurrent threads for data synchronization instances, not the number of concurrent data synchronization instances. To guarantee the number of concurrent data synchronization instances, you must also purchase an exclusive resource group for scheduling. For more information, see Exclusive resource groups for scheduling.
Limitations
Exclusive resource groups for Data Integration are billed by subscription. You cannot delete or release a resource group before its subscription expires. After a subscription expires, the service is suspended and the resource group is released after a specific period.
Exclusive resource groups for Data Integration do not support cross-region use. For example, a resource group in the China (Shanghai) region can only be used by workspaces in China (Shanghai).
Exclusive resource groups for Data Integration do not support Alibaba Cloud classic networks. If your data source is in a classic network, migrate it to a virtual private cloud (VPC) or enable public network access.
Performance metrics
Specification | Maximum concurrent threads for batch synchronization |
4 vCPU 8 GiB | 8 Note
|
8 vCPU 16 GiB | 16 |
12 vCPU 24 GiB | 24 |
16 vCPU 32 GiB | 32 |
24 vCPU 48 GiB | 48 |
Specification | Recommended specification per task |
Real-time synchronization from MySQL with 1 database | 4 vCPU 8 GiB |
Real-time synchronization from MySQL with 2 to 5 databases | 8 vCPU 16 GiB |
Real-time synchronization from MySQL with 6 or more databases | 12 vCPU 24 GiB |
Real-time synchronization from PolarDB-X | 12 vCPU 24 GiB |
Real-time synchronization from Kafka | 4 vCPU 8 GiB |
Other single-table real-time tasks | 4 vCPU 8 GiB |
Specifications and pricing
Exclusive resource groups for Data Integration are billed by subscription. Choose the specification that fits your workload.
Region | Specification | Unit price (CNY/month) |
China (Hangzhou) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Shanghai) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Shenzhen) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Beijing) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Zhangjiakou) | 4 vCPU 8 GiB | 370.00 |
8 vCPU 16 GiB | 738.75 | |
12 vCPU 24 GiB | 1108.75 | |
16 vCPU 32 GiB | 1477.50 | |
24 vCPU 48 GiB | 2216.25 | |
China (Ulanqab) | 4 vCPU 8 GiB | 443.25 |
8 vCPU 16 GiB | 886.50 | |
12 vCPU 24 GiB | 1,329.75 | |
16 vCPU 32 GiB | 1,773.00 | |
24 vCPU 48 GiB | 2,659.50 | |
China (Chengdu) | 4 vCPU 8 GiB | 403.75 |
8 vCPU 16 GiB | 806.25 | |
12 vCPU 24 GiB | 1208.75 | |
16 vCPU 32 GiB | 1611.25 | |
24 vCPU 48 GiB | 2417.50 | |
US (Silicon Valley) | 4 vCPU 8 GiB | 964.38 |
8 vCPU 16 GiB | 1928.78 | |
12 vCPU 24 GiB | 2893.05 | |
16 vCPU 32 GiB | 3857.58 | |
24 vCPU 48 GiB | 5786.10 | |
US (Virginia) | 4 vCPU 8 GiB | 714.79 |
8 vCPU 16 GiB | 1429.58 | |
12 vCPU 24 GiB | 2144.33 | |
16 vCPU 32 GiB | 2859.15 | |
24 vCPU 48 GiB | 4288.65 | |
China (Hong Kong) | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2688.90 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5377.80 | |
Singapore | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2688.90 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5377.80 | |
Germany (Frankfurt) | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2642.25 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5284.50 | |
Malaysia (Kuala Lumpur) | 4 vCPU 8 GiB | 840.00 |
8 vCPU 16 GiB | 1673.75 | |
12 vCPU 24 GiB | 2520.00 | |
16 vCPU 32 GiB | 3346.25 | |
24 vCPU 48 GiB | 5040.00 | |
Indonesia (Jakarta) | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2688.90 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5377.80 | |
Japan (Tokyo) | 4 vCPU 8 GiB | 1026.79 |
8 vCPU 16 GiB | 2047.91 | |
12 vCPU 24 GiB | 3063.38 | |
16 vCPU 32 GiB | 4095.84 | |
24 vCPU 48 GiB | 6126.75 | |
UK (London) | 4 vCPU 8 GiB | 676.25 |
8 vCPU 16 GiB | 1352.50 | |
12 vCPU 24 GiB | 2028.75 | |
16 vCPU 32 GiB | 2705.00 | |
24 vCPU 48 GiB | 4057.50 | |
UAE (Dubai) | 4 vCPU 8 GiB | 1075.00 |
8 vCPU 16 GiB | 2143.75 | |
12 vCPU 24 GiB | 3220.00 | |
16 vCPU 32 GiB | 4288.75 | |
24 vCPU 48 GiB | 6440.00 | |
China North 2 Ali Gov 1 | 4 vCPU 8 GiB | 1020.00 |
8 vCPU 16 GiB | 2005.00 | |
12 vCPU 24 GiB | 2990.00 | |
16 vCPU 32 GiB | 3975.00 | |
24 vCPU 48 GiB | 5945.00 | |
China East 2 Finance, China South 1 Finance | 4 vCPU 8 GiB | 935.75 |
8 vCPU 16 GiB | 1871.50 | |
12 vCPU 24 GiB | 2807.25 | |
16 vCPU 32 GiB | 3743.00 | |
24 vCPU 48 GiB | 5614.50 |
Cost estimation
You can use the DataWorks exclusive resource group calculator to estimate the required specifications and costs. To do this, go to the page in the DataWorks console. You can view information, such as the number of running instances and concurrency, for reference. For more information about how to view the O&M dashboard, see View the O&M dashboard.
Billing
Scale-out and scale-in
You can purchase an exclusive resource group and specify the instance type and number of instances for the resource group. After the purchase, you can scale the resource group out or in. For more information about the procedure and notes on scaling, see Scale out or scale in a resource group.
Change specifications (upgrade or downgrade)
If the current specifications of your exclusive resource group do not meet your business requirements, you can change the specifications. When you change the specifications of a resource group, the specifications of all instances in that resource group are also changed. For more information about the procedure and notes on changing specifications, see Change specifications.
Renew, suspend, and release a resource group
You can renew an exclusive resource group before it expires. You can also allow the resource group to expire. After a resource group expires, its service is suspended and the resource group is automatically released. For more information, see Expiration and renewal.
After a resource group is released, all tasks that depend on the resource group cannot run as expected.
Network connectivity
Like other exclusive resource groups, an exclusive resource group for Data Integration is essentially a set of Alibaba Cloud Elastic Compute Service (ECS) instances. When Data Integration tasks run, you must ensure that the network between the resource group and data sources is connected and not blocked by allowlist or other security access configurations.
After you purchase an exclusive resource group for Data Integration, you must associate it with a VPC. Then, choose a network connectivity solution based on the network environment of your data sources. For more information, see Network connectivity solutions.
Network connectivity solutions
Data source network environment
Network connectivity solution
The data source is on the public network
The data source can be directly connected to the VPC associated with the exclusive resource group.
The data source is in a VPC and in the same region as the exclusive resource group
We recommend that you associate the exclusive resource group with the same VPC as the data source. After the association, the system automatically adds a route to the entire VPC. You can associate any vSwitch in the VPC to enable network connectivity between the exclusive resource group and the data source.
The data source is in a VPC and in a different region from the exclusive resource group
Use Express Connect or VPN Gateway to connect the data source network to the VPC associated with the exclusive resource group, and add a route to the IP address of the destination database to ensure network reachability between the two networks.
The data source is in an on-premises data center
Use Express Connect or VPN Gateway to connect the data source network to the VPC associated with the exclusive resource group, and add a route to the IP address of the destination database to ensure network reachability between the two networks.
The data source is in a classic network
Exclusive resource groups reside in Alibaba Cloud VPCs. If the data source is in a classic network, the network between the data source and the exclusive resource group cannot be connected. We recommend that you migrate the data source to a VPC.
Allowlist configuration
If the data source has an allowlist that restricts access, you must add the IP addresses of the exclusive resource group to the allowlist of the data source to prevent access restrictions. For more information, see Add the resource group to the data source allowlist.
FAQ
For frequently asked questions about DataWorks exclusive resource groups, see Exclusive resource groups.