The data synchronization feature supports multiple types of synchronization topologies. You can plan your synchronization instances based on your business requirements.

One-way synchronization

To ensure data consistency for one-way synchronization, we recommend that you perform only read operations on the objects in the destination instance. Do not modify the objects.

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

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

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

One-way cascade synchronization One-way cascade synchronization

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

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

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

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

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

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

Two-way synchronization

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

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

References