TiCDC

Input—per 1M tokens

Output—per 1M tokens

Context—tokens

WeightsClosed

About

TiCDC is ranked #5 of 30 in database proxy software on Inferse. It runs on API, Linux, macOS, Self-hosted. There is a free plan.

Compared on database proxy software

Deployment model: self-hosteddocs.pingcap.com
Capture method: log-baseddocs.pingcap.com
Schema evolution: Yesdocs.pingcap.com
Initial snapshot: Yesdocs.pingcap.com

Facts

Purpose: TiCDC replicates incremental data from TiDB by capturing TiKV change logs, sorting the changes, and exporting row-based data to downstream systems.docs.pingcap.com · 2 Oct 2026
Disaster recovery: TiCDC can replicate between TiDB clusters with second-level RPO and minute-level RTO.docs.pingcap.com · 2 Oct 2026
Multi-active: TiCDC supports bidirectional replication between TiDB clusters for multi-active deployments.docs.pingcap.com · 2 Oct 2026
Downstream sinks: TiCDC can replicate to TiDB, MySQL-compatible databases, Kafka, Amazon S3, GCS, Azure Blob Storage, and NFS.docs.pingcap.com · 2 Oct 2026
Kafka formats: Recommended Kafka data formats include Canal-JSON, Avro, and Debezium.docs.pingcap.com · 2 Oct 2026
Filtering and management: TiCDC can filter databases, tables, DMLs, and DDLs, and its Open API can query task status, modify task configuration, and create or delete tasks.docs.pingcap.com · 2 Oct 2026
Availability: TiCDC has no single point of failure and supports dynamically adding and deleting TiCDC nodes.docs.pingcap.com · 2 Oct 2026
Delivery semantics: TiCDC outputs each DDL or DML at least once, so failures can cause repeated statements or Kafka messages.docs.pingcap.com · 2 Oct 2026
Index requirement: TiCDC generally replicates only tables with at least one valid index, though the force-replicate option can replicate tables without one.docs.pingcap.com · 2 Oct 2026
Unsupported cases: The docs list RawKV-only clusters, CREATE SEQUENCE and SEQUENCE functionality, and TiDB Lightning physical import on tables being replicated as unsupported scenarios.docs.pingcap.com · 2 Oct 2026
Large transactions: TiCDC only partially supports upstream large transactions, and its new architecture has an out-of-memory risk with extremely large transactions.docs.pingcap.com · 2 Oct 2026
Deployment and scale: TiCDC can be deployed with a new TiDB cluster or added to an existing cluster, and the deployment documentation recommends at least two instances in production.docs.pingcap.com · 2 Oct 2026
Security: The deployment guide documents enabling TLS between TiDB components, including TiCDC.docs.pingcap.com · 2 Oct 2026
Intended users: Documented use cases include disaster recovery, real-time data feeds for monitoring, caching, indexing and analysis, and replication between heterogeneous databases.docs.pingcap.com · 2 Oct 2026