Data Transmission Service:What are DTS serverless instances?

Background information

The serverless model uses a dynamic billing method. Resources are dynamically adjusted at a minute-level granularity based on the instance payload. Billing is performed in real time, and an order is generated every hour. You pay only for what you use, which can result in significant cost savings. Instances that use the serverless billing method are called serverless instances.

A serverless instance dynamically adjusts its resource specifications based on factors such as records per second (RPS), CPU, memory utilization, and network conditions. The adjusted resource specification is measured in DTS Units (DU). After a DU adjustment, the system checks whether the current resource specification meets the payload requirements within 60 seconds.

The following figure shows the resource usage and specification changes for regular instances and serverless instances in a scenario with large fluctuations in data volume:

The figure shows that in a scenario with large business fluctuations:

• Regular instances: More resources are wasted during off-peak periods. Resources are insufficient during peak periods, which can impact your business.

• Serverless instances: The instance resource specifications dynamically scale with the payload. This meets business requirements during both off-peak and peak periods and ensures business continuity.

Advantages

• High elasticity

  Instance resource specifications are adjusted in real time at a minute-level granularity based on the data volume. This improves resource utilization and reduces waste.

• Fully managed

  Instances do not require manual upgrades or downgrades. This improves O&M efficiency and reduces O&M costs for both operations staff and developers.

• Low cost

  Unlike fixed-resource billing, this model provides a true pay-as-you-go experience where resources dynamically scale with the payload. This can result in significant cost savings.

Scenarios

• The data transmission volume is large in the early stages of your business and stabilizes later.

• The data to be transferred has clear peak and off-peak periods throughout the day, and you want to reduce continuous running costs.

• You have existing data transmission tasks and want to purchase new serverless instances or convert regular sync instances to serverless instances.

• The volume of data to be transferred is unpredictable.

• You are an individual developer.

Limits

• The following serverless instance features are in limited preview and are available only to some users.

  • Cross-region or cross-border data synchronization.

  • Two-way synchronization.

  • The Database Type of the source database is Tair/Redis, PolarDB-X 1.0, PolarDB-X 2.0, or MongoDB with a Sharded Cluster.

  • The Database Type of the destination database is Tair/Redis.

• The lower limit for the DU count can be set to 1, 2, 4, 8, 16, or 32. The upper limit can be set to 2, 4, 8, 16, or 32.

Billing description

For more information, see Billing of serverless instances.

Supported regions

This feature is available only in the following regions: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Guangzhou), China (Wuhan - Local Region), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), and Germany (Frankfurt).

Performance

The following table describes the relationship between the performance of a serverless task and the DU count. Actual performance may vary based on factors such as the network environment, the performance of the source and destination database instances, and latency.

Procedural documents

• Configure a serverless instance

• Manage a serverless instance

FAQ

Q: Can I create serverless instances for data migration and change tracking tasks?

A: No, you cannot. Currently, you can create serverless instances only for data synchronization tasks.