Mycat2 vs TiCDC
Mycat2
github.comTiCDC
docs.pingcap.comSide by side
| Figure | Mycat2 | TiCDC |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Database Proxy Software | 7.6 (#13) | 8.1 (#6) |
| Support | The repository links English and Chinese documentation hosted on Yuque. | PingCAP directs paid-plan users to support tickets and all users to community Slack support. |
Plans
In their own words
Mycat2
Mycat2 is free, open-source distributed relational database middleware for Linux and self-hosted deployment. It supports distributed SQL queries and the MySQL communication protocol while connecting to multiple backend databases through the Java ecosystem. Its query engine handles MySQL syntax and value types, rule- and cost-based optimization, and an independent physical execution engine. Data fragmentation is described as improving query processing. Users can customize and load sharding, serial-number and load-balancing algorithms. A project DSL manipulates physical query plans, forwards SQL and caches result sets. The README currently supports Java 8 only. Release notes for v1.22-2022-6-25 list ClickHouse as a backend for SELECT and INSERT, without returning auto-increment values. They also describe SQL permission interception, RSA encryption for user.json, and recycling inactive backend connections after a default 180-second timeout. The repository identifies an Apache License from 2023.8.
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.