Estuary vs TiCDC

Estuary is a managed data integration platform for combining change data capture, batch, streaming, and app synchronization for analytics, operations, and AI. It supports transformations while data is moving, using SQL, Python, or TypeScript, and describes delivery as exactly once with end-to-end latency under 100 milliseconds. More than 200 prebuilt connectors cover databases, warehouses, SaaS apps, and cloud platforms, including Snowflake, BigQuery, Kafka, MySQL, and PostgreSQL. Customers can store data in their own cloud bucket for a duration they choose, and select public, private, or Bring Your Own Cloud deployment. Estuary lists SOC 2 Type II, HIPAA, HITECH, CCPA, and GDPR among its compliance standards, and says data is encrypted in transit and at rest. It is available through API, self-hosted, and web options. The indefinite free tier is limited to 10 GB per month and two concurrent connector instances; paid plans start at $100 a month.

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.