ReplicaDB

ReplicaDB is open source tool for database replication, designed for efficiently transferring bulk data between relational and non-relational databases

Runs with mockssource: GitHubhomepageJavaApache-2.0commit 05ef8d468bcb

Java, Apache-2.0 licensed. The project labels itself: cross platform, database, database replication, elt, etl, fast, java and kafka.

ReplicaDB runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

ReplicaDB CLI builds, packages as fat JAR, launches with --help and --version, and passes 332 offline unit tests (59 classes); server JAR builds but requires Docker/PostgreSQL at runtime which are unavailable 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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
1
last tested
stars
505
forks
114
open issues
1
watchers
19
size
63 MB
created
last push

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.

Time lost to each failure while testing ReplicaDB, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Java JDK 17 not installed6 minutes
  • Maven not installed4 minutes
  • Default JAR had no main manifest1 minute
  • Docker unavailable - 500 Testcontainer tests cannot run in CLI module
  • Docker unavailable - 124 Testcontainer tests cannot run in server module
Install time
16 minutes
Cold machine to finish
18 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
java -jar target/ReplicaDB-1.0.2-jar-with-dependencies.jar --version returned 'Running ReplicaDB version: 1.0.2' and exit code 0; java -jar target/ReplicaDB-1.0.2-jar-with-dependencies.jar --help printed full usage and exit code 0; 332 unit tests passed across 59 test classes (all CLI offline/unit tests); CliOfflineExecutionTest demonstrated end-to-end SQLite-to-SQLite replication working
Model tokens used
385,805
Exact commit tested
05ef8d468bcb
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
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

2. **Built the CLI**: `mvn package -Ptest -DskipTests` produced `target/ReplicaDB-1.0.2-jar-with-de…
3. **Verified the CLI**: `java -jar target/ReplicaDB-1.0.2-jar-with-dependencies.jar --version` ran…
4. **Ran unit tests**: 332 tests passed across 59 test classes (all CLI offline/unit tests). Every …
5. **Built the server module**: `mvn install -DskipTests` (for the CLI artifact as dependency), the…
**Errors hit and fixed:**
| Error | Fix | Time |
|-------|-----|------|
| `java: not found` | Downloaded JDK 17 Temurin | ~6 min |
| `mvn: not found` | Downloaded Maven 3.9.9 | ~4 min |
| `no main manifest attribute` in JAR | Built with `-Ptest` profile to get fat JAR | ~1 min |
| Testcontainers/Docker tests fail (500 in CLI, 124 in server) | No Docker available in container; …
| Server needs PostgreSQL | No Docker; not fixable | — |

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

  • Installed in 16 minutes, faster than the median of the 12 comparable projects Argusic has measured.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 13 cross-platform projects Argusic has installed and timed, ReplicaDB was the 7th fastest to reach a running state, and 10 of 13 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.05

Topics (from GitHub)

cross-platformdatabasedatabase-replicationeltetlfastjavakafkamysqlnosqlnosql-databasesoraclepostgresqlsqltransactional

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/ReplicaDB.svg)](https://argusic.com/subject/replicadb)

Questions

Does ReplicaDB run?
ReplicaDB runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test ReplicaDB?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 05ef8d468bcb. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ReplicaDB?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ReplicaDB take to install?
16 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 ReplicaDB need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ReplicaDB?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ReplicaDB compare with the alternatives?
Of the 13 cross-platform projects Argusic has installed and timed, ReplicaDB was the 7th fastest to reach a running state, and 10 of 13 reached one at all.
Where is the evidence for ReplicaDB?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion