db2rest

Instant no code DATA API platform for relational databases. Connect any database, run anywhere. Power your GENAI application function/tools calls in seconds.

Runssource: GitHubhomepageJavaApache-2.0commit 9971d5dadc8a

Java, Apache-2.0 licensed. The project labels itself: ai, data api, generative ai, java, llm, low code, lowcode and mariadb.

db2rest runs. An Argusic agent installed it in 9 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The project compiles and packages cleanly via mvn -DskipTests clean package, 55 unit tests pass, and the Spring Boot application starts on port 8080 responding with HTTP 200 on /actuator/health.

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
2
last tested
stars
473
forks
100
open issues
35
watchers
10
size
79 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.

Install time
9 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
mvn test ran 55 pure unit tests with 0 failures; curl http://localhost:8080/actuator/health returned HTTP 200 with {"status":"UP"}
Model tokens used
252,023
Exact commit tested
9971d5dadc8a
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.

echo "api-rest unit tests: 9 passed"
echo "Total pure unit tests: 55 passed"
echo "Build: success"
echo "Launch: success (HTTP 200 on /actuator/health)"' in /work/repo
 exited 143 in 0ms:
exec
/bin/sh -lc 'pkill -f "db2rest.jar" 2>/dev/null; kill 1768 2>/dev/null; kill 1713 2>/dev/null; true…
 exited 143 in 0ms:
Here is my final report.
tokens used
252,023
Here is my final report.

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.
  • Nothing broke on the way: zero errors between clone and running.
  • 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 did not, or is not known

  • Took 9 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.

Of the 237 ai projects Argusic has installed and timed, db2rest was the 166th fastest to reach a running state, and 168 of 237 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 9 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner2/3Runs100.000.08
Argusic Runner1/3Did not run20.000.09

Topics (from GitHub)

aidata-apigenerative-aijavallmlow-codelowcodemariadbmysqlmysql-databaseno-codenocodeoraclepostgrespostgresqlrestapispring-bootspringbootsqllite

Embed the badge

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

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

Questions

Does db2rest run?
Yes. db2rest runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test db2rest?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9971d5dadc8a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test db2rest?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does db2rest take to install?
9 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 db2rest need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing db2rest?
Nothing did, in the recorded run: zero errors between clone and running.
How does db2rest compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, db2rest was the 166th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for db2rest?
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.

Discussion