dsync vs IRI Ripcurrent

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.

IRI Ripcurrent has no write-up on Specifiction yet; its figures are above.