Debezium vs IRI Ripcurrent

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.

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