MySQL vs TiCDC
MySQL
mysql.comTiCDC
docs.pingcap.comSide by side
| Figure | MySQL | TiCDC |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | Yes | — |
| Open source | — | Yes |
| Windows | Yes | — |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 18 | 1 |
| Spec score · Database Proxy Software | 9.1 (#1) | 8.1 (#6) |
| Spec score · Data Replication Software | 9.0 (#2) | 8.1 (#11) |
| High availability | MySQL includes Group Replication, InnoDB Cluster and replication features for fault tolerance, failover, scale-out and high availability. | TiCDC has no single point of failure and supports dynamically adding or deleting TiCDC nodes. |
| Support | MySQL Enterprise technical support provides 24x7 direct access to MySQL support engineers. | PingCAP directs paid-plan users to support tickets and all users to community Slack support. |
Plans
MySQL
- Community EditionPrice not published
- Community EditionPriced on request
- Standard EditionPriced on request
- Standard EditionPrice not published
- Enterprise EditionPriced on request
- Enterprise EditionPrice not published
- Cluster Carrier Grade EditionPriced on request
- Cluster Carrier Grade EditionPrice not published
- MySQL Cluster Carrier Grade EditionPriced on request
- MySQL Enterprise EditionPriced on request
In their own words
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.