Decodable vs TiCDC

Decodable is a managed, serverless platform for real-time ETL, ELT, and stream processing, built on Apache Flink and Debezium. It lets teams create pipelines in SQL, Java, or Python and manage them through a UI, CLI, APIs, or dbt. SQL supports transformations, filtering, stateful joins, and complex event processing. Pipelines process data exactly once by default and can resume after a stop or failure. Connectors include Apache Kafka, PostgreSQL, Apache Iceberg, and Snowflake, with Debezium-powered change data capture. Teams can use Decodable-hosted infrastructure or a Bring Your Own Cloud deployment. The free plan costs nothing and does not expire or require a credit card; it includes 24 hours or 10GiB of stream retention, 20 streams, and four running tasks. On Demand costs $0.12 a month, billed monthly, and Enterprise costs $0.10 a year, billed annually with committed capacity. Decodable is available via API, web, and self-hosted deployment.

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.