You can use Data Transmission Service (DTS) to migrate and synchronize data from PolarDB-X 2.0 to Tablestore.
Background information
Data Transmission Service (DTS) is a real-time data streaming service from Alibaba Cloud. It supports data exchange between various data sources, such as relational databases (RDBMS), NoSQL databases, and online analytical processing (OLAP) systems. DTS integrates features such as data synchronization, migration, subscription, integration, and processing to help you build a secure, scalable, and highly available data architecture. For more information, see Data Transmission Service (DTS).
Scenarios
Big data analytics and processing
To analyze large amounts of business data from PolarDB and generate reports, you can migrate the data to Tablestore. Tablestore features a distributed architecture with high-concurrency read and write capabilities, which supports fast data analytics and ad hoc queries. Tablestore is ideal for big data business intelligence (BI) and OLAP scenarios.
Log and event data processing
To process large volumes of log and event data from internet services, IoT devices, or applications, you can migrate the data to Tablestore. This allows for more efficient storage and analysis. Tablestore is ideal for semi-structured or unstructured data and simplifies tasks such as log analysis, monitoring, alerting, and trend prediction.
Cost optimization and archiving
As your data volume grows, you can migrate historical data that is not frequently accessed from a costly relational database to Tablestore. This reduces storage costs while ensuring the data remains accessible for compliance audits or historical analysis.
Data import solutions
You can select an import solution based on your data migration scenario.
Import solution | Description |
Data migration is primarily used for moving data to the cloud. For example, you can migrate data from on-premises databases, self-managed databases on ECS instances, or third-party cloud databases to Alibaba Cloud databases. Data migration is a one-time task. After the migration is complete, you can release the instance. Migration types include schema migration, full migration, and incremental migration. Incremental migration offers some data synchronization features but is less flexible. For example, it does not support modifying synchronization objects online or performing two-way synchronization. | |
Data synchronization provides real-time data synchronization between two data sources. It is used for scenarios such as active geo-redundancy, data disaster recovery, cross-border data synchronization, query and report offloading, cloud BI, and real-time data warehouses. Data synchronization is a continuous task. After you create the task, it runs continuously to keep the data in the source and destination consistent. Synchronization types include schema synchronization, full synchronization, and incremental synchronization. |
How data import works
How data migration works
Data migration consists of three phases: schema migration, full data migration, and incremental data migration. To keep the source database operational during the migration, you can select all three migration types when you configure the task.
How data synchronization works
DTS synchronizes data changes between two data sources in real time. It is often used to transfer data from an online transactional processing (OLTP) database to an OLAP database. Data synchronization consists of two phases:
Initial synchronization: DTS begins by collecting incremental data, and then loads the structure and historical data from the source database to the target database.
Real-time data synchronization: After the initial synchronization is complete, DTS continuously synchronizes data changes to keep the source and destination databases consistent.
Billing
Data migration
Migration type | Link configuration fee | Data transfer cost |
Schema migration and full data migration | Not charged. | Not charged in this example. |
Incremental data migration | Charged. For more information, see Billing overview. |
Data synchronization
Synchronization type | Pricing |
Schema synchronization and full data synchronization | Free of charge. |
Incremental data synchronization | Charged. For more information, see Billing overview. |
Tablestore
When you import data into Tablestore, you are charged a storage fee based on the data volume.
When you access Tablestore using a migration tool, Tablestore charges fees for read and write operations based on the selected billing method.
Billing mode
Compute capacity description
Purchase reserved Virtual Compute Units (VCUs) based on your resource assessment. You can also enable elastic capacity and pay for compute performance based on actual usage. Compute capacity covers the consumption for data reads and writes.
Pay for read and write requests based on read/write throughput. Billing differs for pay-as-you-go and reserved read/write CUs depending on the instance type.
NoteFor more information about instance types and CUs, see Instances and Read/write throughput.