ApsaraDB RDS provides three data movement capabilities — migration, synchronization, and data subscription — for one-time cloud migrations, continuous replication, and real-time change data capture.
Which capability do you need?
|
Capability |
What it does |
Typical use case |
|
Migration |
Transfers a database from one location to another. Supports full load only, or full load followed by incremental sync to minimize downtime. |
Move an on-premises or self-managed database to ApsaraDB RDS |
|
Synchronization |
Keeps two databases in sync continuously. Supports unidirectional and bidirectional replication. |
Build an active-active architecture or maintain a read replica in another region |
|
Data subscription |
Streams incremental changes (inserts, updates, deletes) from a database to a consumer application. |
Feed a real-time data warehouse, invalidate a cache, or drive event-driven workflows |
Scenarios
Zero-downtime cloud migration
Use migration to move an on-premises or ECS-hosted database to ApsaraDB RDS with minimal downtime. Full load followed by incremental sync keeps the source database running until you cut over, reducing the switchover window to minutes.
Active-active geo-redundancy
Use synchronization to build a geo-redundant architecture with bidirectional replication between ApsaraDB RDS instances in different regions. Both instances stay writable, and Data Transmission Service (DTS) automatically resolves conflicts.
Real-time data feeds
Use data subscription to stream change data capture (CDC) events from ApsaraDB RDS to downstream systems such as AnalyticDB, ClickHouse, or Redis. Consumers receive an ordered stream of row-level changes without querying the source database.