You need to enable JavaScript to run this app.
Database Transmission Service

Database Transmission Service

Copy page
Download PDF
Overview
What is Database Transmission Service
Copy page
Download PDF
What is Database Transmission Service
Database Transmission Service (DTS) is a data stream service that integrates data migration, data synchronization, and data subscription. It supports data interaction between data sources such as relational databases and non-relational databases, reducing the complexity of data circulation between databases. It helps you seamlessly migrate databases to the cloud without interrupting business operations, easily build high-availability database disaster recovery architectures through real-time synchronization channels. At the same time, you can freely consume real-time incremental data from cloud databases via data subscription based on your needs.​
Product features​
  • One-stop data flow service: supports multi-mode migration and synchronization, compatible with mainstream databases like MySQL, PostgreSQL, MongoDB and Redis.​
  • Zero-downtime data verification: Performs precise checks and comparisons of data differences between source and target databases without service interruption, accurately identifying structural discrepancies.​
  • Pre-migration assessment: Provides pre-evaluation before migration to identify potential issues in advance, reduce migration risks, and improve success rates.​
  • Real-time uncremental data subscription: Supports multiple database types with on-demand data consumption, well-suited for asynchronous business decoupling scenarios.​
Product advantages​
DTS supports data transmission of relational and non-relational databases. Compared with third-party migration tools, DTS can more conveniently create and manage rich, high-performance, high-security and reliable transmission links.​
  • Rich and diverse scenarios​
  • It supports the migration of multiple database engines, and the business interruption time window caused by the migration is shortened to the minute.​
  • It supports data transmission through public and virtual private cloud networks.​
  • It supports the migration task configuration only to incremental migration, realizing pure incremental synchronization from the source database to the target database.​
  • Easy to operate and visualize​
  • It provides a visual management interface and a wizard-based task configuration, allowing customers to easily complete data migration.​
  • The migration progress is quantitatively displayed, and the console displays the full migration percentage and incremental migration data delay.​
  • The migration rate of full and incremental migration is displayed graphically, and the link specifications can be adjusted in real time to maximize the utilization of link resources.​
  • Secure and reliable data​
  • The instance is highly available, and the node has a high degree of recovery and healing capabilities, with recovery in seconds.​
  • It supports breakpoint transmission. After the link exception is interrupted and returns to normal, it can automatically append the data of the interrupted time period.​
  • Full and incremental integration: Supports deduplication and concurrent synchronization of both full and incremental data, improving transmission speed and minimizing data rollback risks.​
  • AI data pipeline: Supports heterogeneous data synchronization between MySQL and Milvus and other sources, with built-in automated vectorization capabilities that eliminate the need for additional service deployment, significantly reducing the cost of building and maintaining AI data pipelines.​
Architecture principles​
DTS provides a non-stop migration solution and supports multiple migration types, such as schema migration, full data migration, and incremental data migration.​
  • Data migration​
  • ​​​
  • Schema migration: Reads the source database and table schema definition syntax and reassembles it into the syntax format of the target database.​
  • Full migration: Fully read the content of the source table and write it to the corresponding target table.​
  • Incremental migration: Parses and replays the target database incremental log to achieve online data migration.​
  • Post-schema migration: To ensure the performance of data migration and the stability of the migration task, some database migration object will be created after the incremental migration is complete. The objects that need to undergo post-schema migration include:​
  • RDS for MySQL: trigger, event.​
  • RDS for PostgreSQL: ordinary trigger, event trigger, RULE, exclusive constraint, foreign key constraint, check constraint, Domain constraint, and Sequence value setting.​
tip​
Currently, the full-incremental feature is only supported for RDS for MySQL migration tasks. The architecture of tasks with this feature enabled differs from that of tasks without it. For details, refer to What is full-incremental feature?.​
  • Data synchronization​
  • ​
  • ​​​
​
  • Schema initialization: Reads the source database and table schema definition syntax and reassembles it into the syntax format of the target database.​
  • Full initialization: Fully read the content of the source table and write it to the corresponding target table.​
  • Incremental synchronization: Parses and replays the target database incremental log to achieve online data synchronization.​
tip​
Currently, the full-incremental feature is only supported for RDS for MySQL synchronization tasks. The architecture of tasks with this feature enabled differs from that of tasks without it. For details, refer to What is full-incremental feature?.​
  • Data subscription​
  • ​
  • ​​​
​
  • Full subscription: Fully reads the content of the source table and converts it into a ProtoBuf structure. Currently only supports Volcano Engine Proto, Canal Proto, Canal JSON, or Avro formats, and pushes it to the corresponding message queue.​
  • Incremental subscription: Resolves the incremental logs of the source database and converts them into a ProtoBuf structure. Currently only supports Volcano Engine Proto, Canal Proto, Canal JSON, or Avro formats, and pushes them to the corresponding message queue.​
  • Database and table schema subscription: Converts the source database and table schema into a ProtoBuf structure. Currently only supports Volcano Engine Proto, Canal Proto, Canal JSON, or Avro formats, and pushes it to the corresponding message queue.​
Application scenarios​
DTS supports the application scenarios of smooth database migration. Its incremental migration feature ensures business continuity, synchronizes data changes in real time, and reduces downtime to the minute level. For details, refer to Application scenarios.​
​
Last updated: 2026.09.02 16:10:46