debezium
Change data capture for a variety of databases. Please log issues at https://github.com/debezium/dbz/issues.
Runssource: GitHubhomepageJavaApache-2.0commit 841f3a72747e
Java, Apache-2.0 licensed. The project labels itself: apache kafka, cdc, change data capture, data pipeline, database, debezium, event streaming and hacktoberfest.
debezium runs. An Argusic agent installed it in 33 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Debezium 3.7.0-SNAPSHOT builds and its unit test suites for the PostgreSQL (136 tests) and MySQL (582 of 583 tests) connectors pass on a user-installed Temurin JDK 21; only tests requiring a Docker engine/Kafka broker cannot run in this container.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No JDK installed and no JDK on filesystem; Maven wrapper could not run (JAVA_HOME undefined)3 minutes
- debezium-connector-mysql unit tests: KafkaSchemaHistoryTest failed with 'Could not find a valid Docker environment' because the container has no Docker daemon (/var/run/docker.sock absent, no podman/nerdctl)1 minute
- Sheeted POM-model warnings '[ERROR] dependencyManagement...tools.jar must specify an absolute path but is ${tools.jar}' from old Glassfish JAXB POMs during dependency resolution
- Install time
- 33 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- ./mvnw -B clean install -Dquick exited 0 with BUILD SUCCESS across 63 modules; then 'mvnw -B -pl debezium-connector-postgres -DskipITs test' exited 0 with Tests run: 136, Failures: 0, Errors: 0, Skipped: 4; then 'mvnw -B -pl debezium-connector-mysql -DskipITs test' reported Tests run: 583, Failures: 0, Errors: 1, Skipped: 4 where the single error is the Docker-unavailable KafkaSchemaHistoryTest
- Model tokens used
- 117,320
- Exact commit tested
- 841f3a72747e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: [INFO] BUILD SUCCESS debezium-connector-postgres/target/debezium-connector-postgres-3.7.0-SNAPSHOT-sources.jar debezium-connector-postgres/target/debezium-connector-postgres-3.7.0-SNAPSHOT-test-sources.jar debezium-connector-postgres/target/debezium-connector-postgres-3.7.0-SNAPSHOT-tests.jar debezium-connector-mysql/target/debezium-connector-mysql-3.7.0-SNAPSHOT-sources.jar debezium-connector-mysql/target/debezium-connector-mysql-3.7.0-SNAPSHOT-test-sources.jar debezium-connector-mysql/target/debezium-connector-mysql-3.7.0-SNAPSHOT-tests.jar All verification steps are complete: the full build succeeded, unit tests ran, and the only failure… tokens used 117,320 All verification steps are complete: the full build succeeded, unit tests ran, and the only failure…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 33 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
apache-kafkacdcchange-data-capturedata-pipelinedatabasedebeziumevent-streaminghacktoberfestkafkakafka-connectkafka-producer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/debezium)Questions
- Does debezium run?
- Yes. debezium runs. Argusic installed and launched it on a clean machine in 33 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test debezium?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 841f3a72747e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test debezium?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does debezium take to install?
- 33 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does debezium need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing debezium?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for debezium?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.