dbmazz vs Google Cloud Datastream

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.

Google Cloud Datastream is a serverless change data capture and replication service for synchronizing data. Streams can capture ongoing updates and backfill historical records, while the service scales automatically without resources for users to provision or manage. Supported destinations include BigQuery, Cloud Storage, and Apache Iceberg tables. Documented sources include Oracle, MySQL, PostgreSQL, AlloyDB, SQL Server, MongoDB, Spanner, Salesforce, ServiceNow, Workday, and Microsoft Dataverse; some sources are marked as preview. Datastream can work with Dataflow templates to load data from Cloud Storage into destinations including BigQuery, Cloud SQL, and Spanner. Connectivity options include IP allowlisting, a forward SSH tunnel, and private connectivity over VPC peering. Processing is charged, idle streams incur no cost, and other Google Cloud resources are billed separately. The free tier includes 100 GiB of eligible CDC data per month per billing account. Events are delivered at least once, but ordering is not guaranteed. Datastream is administered through the Google Cloud console, CLI, or REST API.