DBLE vs TiCDC
DBLE
opensource.actionsky.comTiCDC
docs.pingcap.comSide by side
| Figure | DBLE | 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.8 (#7) | 8.1 (#6) |
| High availability | The DBLE server can run as a cluster so business workloads do not suffer from a single-node failure. | TiCDC has no single point of failure and supports dynamically adding or deleting TiCDC nodes. |
| Purpose | DBLE is high-scalability middleware for MySQL sharding. | TiCDC replicates incremental data from TiDB by capturing TiKV change logs, sorting the changes, and exporting row-based data to downstream systems. |
| Support | The DBLE documentation lists community support resources and says commercial support is available by contacting the maker. | PingCAP directs paid-plan users to support tickets and all users to community Slack support. |
Plans
In their own words
DBLE
DBLE is free, open-source middleware for scaling MySQL through sharding. It uses the MySQL protocol and can replace MySQL in many cases without application code changes. Teams can configure hash, modulo, time-based, range-based, or custom sharding, along with global and ER tables. DBLE lists query routing, connection pooling, load balancing, automatic failover, read/write separation, master-slave expansion, and ZooKeeper cluster deployment. SQL support includes SQL 92 and MySQL dialect features such as joins, unions, grouping, ordering, and distinct queries; some features remain on its roadmap. Query optimization addresses global-table joins, sharded tables, ER relations, and subqueries. Distributed transactions use two-phase commit in normal or XA modes, with XA depending on MySQL 5.7 XA transactions, backend availability, and disk reliability. Security controls include password encryption, IP allowlists, and SQL denylists. Explain plans, MySQL-compatible slow logs, and slow-query reports support operations. DBLE is self-hosted on Linux and GPL-2.0 licensed. The open-source plan costs nothing.
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.