OpenLogReplicator vs TiCDC

OpenLogReplicator is a free, open-source Oracle change data capture solution written in C++ for self-hosted Linux deployments. It reads transactions directly from Oracle binary redo logs and streams changes as JSON or Protobuf. Destinations include Kafka, flat files, plain TCP/IP or ZeroMQ network streams, and a discard output for testing. The log-based design is intended to minimize impact on the source database. Archived redo logs can be processed, including offline operation while the database is shut down, and actual DDL commands can be tracked. Basic DML filters can restrict processing, such as selecting INSERT operations for a table. Direct Prometheus metrics include DML counters that can carry schema-name tags. Oracle 23c is supported; binary XMLType support for Oracle 11.2 through 21c is experimental. Debezium use is supported with version 1.3.0 as the minimum and 1.9.0 recommended for Debezium 2.x and 3.x. The GPL v3 plan costs nothing.

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.