OpenLogReplicator vs PeerDB
OpenLogReplicator
bersler.comPeerDB
peerdb.ioSide by side
| Figure | OpenLogReplicator | PeerDB |
|---|---|---|
| Price from | Free | $250/mo |
| Free plan | Yes | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Linux | Yes | — |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 5 |
| Spec score · Change Data Capture Software | 7.6 (#13) | 7.9 (#10) |
| Purpose | OpenLogReplicator is an open-source Oracle database change data capture solution written in C++. | PeerDB streams data from Postgres to data warehouses, queues, and storage engines. |
| Support | Production assistance and proof-of-concept help are available by contacting the author through the contact form. | PeerDB provides documentation and a community Slack for questions, while paid plans include implementation support and certain plans include 24x7 production support with SLAs. |
Plans
PeerDB
- Open sourceFree
- Micro$250 a month
- Small$1,000 a month
- Medium$2,000 a month
- Large$4,000 a month
In their own words
OpenLogReplicator
OpenLogReplicator is a free, open-source Oracle change data capture solution written in C++ for self-hosted Linux deployments. It reads transactions directly from Oracle binary redo logs and streams changes as JSON or Protobuf. Destinations include Kafka, flat files, plain TCP/IP or ZeroMQ network streams, and a discard output for testing. The log-based design is intended to minimize impact on the source database. Archived redo logs can be processed, including offline operation while the database is shut down, and actual DDL commands can be tracked. Basic DML filters can restrict processing, such as selecting INSERT operations for a table. Direct Prometheus metrics include DML counters that can carry schema-name tags. Oracle 23c is supported; binary XMLType support for Oracle 11.2 through 21c is experimental. Debezium use is supported with version 1.3.0 as the minimum and 1.9.0 recommended for Debezium 2.x and 3.x. The GPL v3 plan costs nothing.
PeerDB
PeerDB streams data from Postgres to data warehouses, queues, and storage engines, using one-way replication. Its supported methods include log-based change data capture, cursor-based replication with timestamps or integers, and XMIN-based replication. A Postgres-compatible SQL interface supports ETL and data movement, and PeerDB handles Postgres data types such as jsonb, arrays, and PostGIS, as well as TOAST columns and schema changes. The actively maintained source connectors are PostgreSQL, MySQL, MongoDB, CockroachDB, and BigQuery; actively maintained destinations are ClickHouse, ClickHouse Cloud, and Postgres. Snowflake, BigQuery, Elasticsearch, Kafka, Redpanda, Confluent, Azure Event Hubs, Google Pub/Sub, and S3 destinations are deprecated and no longer actively maintained. PeerDB is available for free deployment under the AGPL-3.0 license. Paid plans start at $250/mo for Micro, which allows up to two vcores and is recommended for up to 50 million rows moved per month. Larger plans list higher row-volume recommendations and vcore limits. PeerDB states that it is 10x faster than existing tools and reports SOC 2 Type II and GDPR compliance.