ApsaraDB RDS supports migration, synchronization, and data subscription to help you move databases to the cloud, replicate data continuously, and capture changes in real time.
Which capability do you need?
|
Capability |
What it does |
Typical use case |
|
Migration |
Moves a database from a source to a destination. Supports full-load migration or full load plus 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. Full load plus 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 ordered, row-level changes without querying the source database.