Data Transmission Service (DTS) tracks data changes from your databases in real time. After DTS captures changes, you can consume the tracked data and write it to a destination database. Change tracking is commonly used in the following scenarios:
-
Cache updates: Keep caches in sync with the source database without polling.
-
Asynchronous business decoupling: Decouple upstream and downstream systems by consuming change events independently.
-
Heterogeneous data synchronization: Replicate data between databases of different types or structures.
-
ETL pipelines: Feed change data into extract, transform, and load (ETL) workflows for data warehousing or analytics.
Supported databases
Cross-account change tracking support depends on the access method and type of the source database. To create a change tracking task across Alibaba Cloud accounts, set the Replicate Data Across Alibaba Cloud Accounts parameter to Yes for the source database. For supported databases, see the Supported databases section in "Configure a DTS task across Alibaba Cloud accounts."
| Source database | Versions | Data change types | Reference |
|---|---|---|---|
| Self-managed MySQL database | 5.1, 5.5, 5.6, 5.7, and 8.0 | Data update, Schema update | Track data changes from an ApsaraDB RDS for MySQL instance |
| ApsaraDB RDS for MySQL | All versions | Data update, Schema update | Track data changes from an ApsaraDB RDS for MySQL instance |
| PolarDB for MySQL | All versions | Data update, Schema update | Track data changes from a PolarDB for MySQL cluster |
| PolarDB-X 1.0 | — | Data update, Schema update | Track data changes from a PolarDB-X 1.0 instance |
| PolarDB-X 2.0 | — | Data update, Schema update | Track data changes from a PolarDB-X instance |
| PolarDB for PostgreSQL (Compatible with Oracle) | All versions | Data update | Track data changes from a PolarDB for Oracle cluster |
| Self-managed Oracle database | 9i, 10g, and 11g | Data update, Schema update | Track data changes from a self-managed Oracle database |
| ApsaraDB RDS for PostgreSQL | 9.4, 10, 11, 12, 13, 14, 15, and 16 | Data update | Track data changes from an ApsaraDB RDS for PostgreSQL instance |
| Self-managed PostgreSQL database | 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, and 16.x | Data update | Track data changes from an ApsaraDB RDS for PostgreSQL instance |
| Data Management (DMS) logical database | — | Data update | Track data changes from a DMS logical database |
| PolarDB for PostgreSQL | 11 and 14 | Data update, Schema update | Track data changes from a PolarDB for PostgreSQL cluster |
Constraints:
-
PolarDB-X 1.0 and PolarDB-X 2.0: The database must be created based on ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X databases created based on PolarDB for MySQL clusters.
-
DMS logical database: The logical database must be created based on database shards of multiple PolarDB for MySQL clusters.
-
Self-managed Oracle database: Non-RAC architecture only.