The data synchronization mode of Data Transmission Service (DTS) supports multiple types of synchronization topologies. You can design and deploy your data synchronization instances based on your use cases.

One-way replication

To ensure data consistency between systems that are synchronized by using a one-way replication, we recommend that you perform only read operations on the target database.

Topology type Topology Description
One-way, one-to-one replication One-way one-to-one synchronization None
One-way, one-to-many replication One-way one-to-many synchronization

You must purchase multiple data synchronization instances to implement one-way, or one-to-many replications.

For example, if you want to replicate data from Instance A to Instances B, C, and D in parallel, you must purchase three data synchronization instances.

One-way cascading One-way cascade synchronization

You must purchase multiple data synchronization instances to implement one-way cascading.

For example, if you want to replicate data from Instance A to Instance B and then from Instance B to Instance C, you must purchase two data synchronization instances.

One-way many-to-one synchronization One-way many-to-one synchronization

You must purchase multiple data synchronization instances to implement one-way or, many-to-one replications.

For example, if you want to replicate data from Instance B, C, and D to Instance A, you must purchase three data synchronization instances.

Note To ensure data consistency, you must select different sets of objects for these data synchronization instances.

Two-way replication

DTS only supports two-way replication between two MySQL databases. DTS does not support two-way replication between multiple MySQL databases.
Note
Topology type Topology Description
Two-way, one-to-one replication Two-way data synchronization

To ensure data consistency, make sure that records with the same primary key value or unique key value are updated only on one of the databases.

References