Canal vs dbmazz

Canal is a free, self-hosted project that parses MySQL binary logs so applications can subscribe to and consume database changes incrementally. It acts like a MySQL replica, requesting binlog data from a master and parsing the events. Listed uses include database mirroring and real-time backup, index maintenance, cache refresh, and business-logic processing. The README lists source versions MySQL 5.1.x, 5.5.x, 5.6.x, 5.7.x, and 8.0.x. Canal can send change records to Kafka and RocketMQ; the quick start also lists RabbitMQ and Pulsar server modes. Its Protocol Buffers 3.0 client-server design has clients for Java, C#, Go, and Python. Canal Admin provides a web interface for managing configuration, tasks, and logs, and the project lists native Prometheus monitoring. Docker images and a Docker QuickStart are available, but the default setup runs only one Canal instance per Docker instance. The project is licensed under Apache-2.0.

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.