dbmazz vs TiCDC
dbmazz
github.comTiCDC
docs.pingcap.comSide by side
| Figure | dbmazz | TiCDC |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · Change Data Capture Software | 8.0 (#9) | 8.1 (#8) |
| Intended users | The README describes dbmazz as an option for teams seeking streaming PostgreSQL CDC without operating a streaming platform. | Documented use cases include disaster recovery, real-time data feeds for monitoring, caching, indexing and analysis, and replication between heterogeneous databases. |
| Support | The project points users to GitHub Discussions and Issues, and its documentation lists support by email or GitHub issue. | PingCAP directs paid-plan users to support tickets and all users to community Slack support. |
| What it does | dbmazz is a Rust daemon that reads PostgreSQL changes through logical replication and streams inserts, updates, and deletes to a sink. | TiCDC captures TiKV change logs, orders them, and exports row-level incremental changes from TiDB to downstream systems. |
Plans
In their own words
dbmazz
dbmazz is a Rust daemon for moving database changes into a sink. It reads PostgreSQL changes through logical replication and streams inserts, updates, and deletes. The project lists PostgreSQL and MySQL as sources, and StarRocks, PostgreSQL, and Snowflake as stable sinks; S3/Iceberg is planned. Each instance handles one replication job. The project reports sub-second replication lag and about 11 MB of resident memory per daemon. Teams can try its ez-cdc CLI quickstart or run the daemon from the official Docker image. The CLI supports Linux and macOS on amd64 and arm64. Listed observability tools include Prometheus metrics, gRPC reflection, an HTTP control plane, and a live terminal dashboard. Automatic setup can create publications, replication slots, sink tables, and audit columns. Self-hosting is free; BYOC is also listed at free in a customer's AWS or GCP account, while support and optional PrivateLink cost extra. The Elastic License 2.0 permits commercial and non-commercial use but restricts offering the software to third parties as a managed service.
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.