Change Content

The DataWorks Data Service API can run on a Shared Data Service Resource Group, an Exclusive Data Service Resource Group, or a Serverless Resource Group. The Shared Data Service Resource Group is shared by tenants and supports only data sources on the public or classical network. For a long time, The Shared Data Service Resource Group is recommended only for temporary testing purposes and is not recommended for production scenarios. To improve resource isolation, network connectivity, disaster recovery, and high availability of online services, the Shared Data Service Resource Group is planning to go offline.

• Starting from March 1, 2025, new APIs will stop using the DataWorks Shared Data Service Resource Groups. Existing APIs that have been configured with the DataWorks Shared Data Service Resource Groups will not be affected and will retain normal functions.
• Starting from October 1, 2025, APIs that have been configured with DataWorks Shared Data Service Resource Groups will no longer support modification unless switched to the DataWorks Serverless Resource Group.
• Starting from April 1, 2026, DataWorks Shared Data Service Resource Groups will no longer provide services, and APIs that have been configured with the DataWorks Shared Data Service Resource Groups will not be able to be called normally.

It is recommended that you change the resource group of the Data Service API to the DataWorks Serverless Resource Group as soon as possible. The DataWorks Serverless Resource Group will provide more stable, efficient, and secure services for your Data Service API.

Change Impact

You can follow the steps and documentation below to replace the DataWorks Shared Data Service Resource Group with the DataWorks Serverless Resource Group:

1. Purchase the DataWorks Serverless Resource Group.
2. Configure the network for the DataWorks Serverless Resource Group (it is recommended to bind two sets of availability zones and VSwitches for Data Service).
3. Perform quota management for the DataWorks Serverless Resource Group and allocate available CUs for Data Service.
4. Batch change the Data Service API resource group to the DataWorks Serverless Resource Group.
5. Test, submit, and publish Data Service APIs.