Amazon RDS vs TiCDC
Amazon RDS
aws.amazon.comTiCDC
docs.pingcap.comSide by side
| Figure | Amazon RDS | TiCDC |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | Yes | — |
| Open source | — | Yes |
| Web | Yes | — |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 6 | 1 |
| Spec score · Database Proxy Software | 8.9 (#3) | 8.1 (#6) |
| Founded | 2006 | 2015 |
| Headquarters | Seattle, Washington, United States | Sunnyvale, California, USA |
| High availability | Multi-AZ deployments synchronously replicate data and automatically fail over to a standby instance. | TiCDC has no single point of failure and supports dynamically adding or deleting TiCDC nodes. |
| Licence | Amazon RDS is a proprietary hosted AWS service; the database engines it hosts may be open-source or commercial under their respective licences. | The public TiCDC repository is licensed under Apache-2.0. |
| System requirements | RDS is accessed as an AWS cloud service through web console, CLI, API or database drivers rather than installed locally. | Production guidance recommends at least 16 CPU cores, 64 GB memory, a 500 GB SSD, a 10-Gigabit network card, and two TiCDC instances. |
| What it does | Amazon RDS is a managed relational database service that sets up, operates and scales databases in AWS while handling common administration. | TiCDC captures TiKV change logs, orders them, and exports row-level incremental changes from TiDB to downstream systems. |
Plans
Amazon RDS
- AWS Free TierFree
- AWS Free Tier for RDSFree
- On-demandPrice not published
- On-Demand InstancesPrice not published
- Reserved InstancePrice not published
- Reserved InstancesPrice not published
In their own words
Amazon RDS
Amazon RDS has no write-up on Specifiction yet; its figures are above.
TiCDC
TiCDC is a free, open-source, self-hosted tool for replicating incremental data changes from TiDB. It captures TiKV change logs, sorts the changes, and exports row-based data to systems including TiDB, MySQL-compatible databases, Kafka, Amazon S3, GCS, Azure Blob Storage, and NFS. Recommended Kafka formats include Canal-JSON, Avro, and Debezium. Filters can select databases, tables, DMLs, and DDLs, while the Open API can check task status, change task configuration, and create or delete tasks. TiCDC supports replication between TiDB clusters for disaster recovery, with second-level RPO and minute-level RTO, as well as bidirectional replication for multi-active deployments. It can be deployed with a new cluster or added to an existing one; production guidance recommends at least two instances. The system has no single point of failure and allows nodes to be added or removed dynamically. Delivery is at least once, so failures can lead to repeated statements or Kafka messages.