Debezium vs dsync
Debezium
debezium.io
dsync
adiom.ioSide by side
| Figure | Debezium | dsync |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Database Replication Software | 8.9 (#2) | 8.3 (#6) |
| Change capture | Its log-based CDC captures inserts, updates, and deletes with low delay, without requiring changes to the data model. | After an initial sync, dsync monitors the source for changes and updates the destination. |
| Deployment | The most common deployment uses Apache Kafka Connect; Debezium can also be embedded in JVM applications or run through Debezium Server. | The open source edition is a single binary that can run on a laptop, VM, or Docker container. |
| Intended users | The project describes itself as an open-source platform and welcomes community participation in using, discussing, and developing it. | Adiom describes dsync as intended for engineers and DevOps teams at enterprises and fast-growing companies. |
| Purpose | Debezium is an open source distributed platform for change data capture that streams database row changes to applications. | dsync migrates and replicates data between databases and data stores, including one-time migrations and continuous replication. |
| Support | The project points users to its documentation, user chat room, and Google Group for questions. | Adiom offers commercial support for both open source dsync and its Enterprise version. |
Plans
In their own words
Debezium
Debezium captures row-level database changes and delivers them to applications as events, so they can respond to inserts, updates, and deletes. Its connectors use database logs for low-delay capture without requiring changes to the data model, and can take initial or incremental snapshots, filter schemas, tables, and columns, and mask selected values. Listed databases include MongoDB, MariaDB, MySQL, PostgreSQL, SQL Server, Oracle, Db2, and Cassandra. Connectors for Vitess, Spanner, Informix, CockroachDB, YashanDB, Ingres, and Milvus are marked incubating and may change without backward compatibility. A common deployment uses Apache Kafka Connect; Debezium can also run through Debezium Server or as a library in JVM applications. Debezium Server can send serialized events to Amazon Kinesis, Google Cloud Pub/Sub, and Apache Pulsar. Ready-to-use transformations support routing, filtering, and event flattening. Debezium is free under the Apache Software License 2.0. Its quay.io container images are for testing and evaluation, not production.
dsync
dsync moves data between databases and other data stores through one-time migrations or ongoing, one-way replication. After the initial copy, it can watch the source and apply later changes at the destination. The open source edition is a single binary that can run on a laptop, VM, or Docker container. Connectors include MongoDB, Cosmos DB, DynamoDB, AWS DocumentDB, PostgreSQL, S3, and CSV files; several others are still in preview or development. Checks range from quick namespace counts to full hash-based verification, and saved state lets an initial copy or change-capture flow resume. Progress appears in the CLI and a web page hosted on the machine running dsync. Adiom says dsync does not store data and supports network encryption. Transformations can use external processes connected over gRPC. It does not replicate source DDL statements or indexes. With a metadata store for resumability, the open source version has a 16 MB read-plan cap. Enterprise adds horizontal scalability, observability, and transformations. The open source plan is free.