resgate

A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.

Runssource: GitHubhomepageGoMITcommit 0cab702e09ff

Go, MIT licensed. The project labels itself: api gateway, go, golang, microservices, microservices architecture, nats server, realtime and resgate.

resgate runs. An Argusic agent installed it in 4 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Resgate 1.8.0 builds from source (go build), its full test suite passes (226/226), and the binary starts bound to a real NATS server and responds to HTTP requests on port 8080.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
739
forks
69
open issues
16
watchers
24
size
2 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 resgate, 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.

  • Go not found in container2 minutes
  • NATS server not found1 minute
  • NATS server process died after shell command ended1 minute
  • Resolve of localhost to IPv6 when NATS only listened on IPv41 minute
Install time
4 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go test ./... exited 0, 226 passed (223 in test/, 3 in server/); curl http://127.0.0.1:8080/ returned HTTP 400 (expected RES protocol path), curl http://127.0.0.1:8080/api/ returned 404 with valid JSON error response; resgate binary ran against real NATS server and accepted connections on port 8080
Model tokens used
164,237
Exact commit tested
0cab702e09ff
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.

tokens used
164,237
All done. Here's my summary:
**Installed dependencies**: Downloaded Go 1.22.5 and NATS server 2.10.22 binaries (no root, no syst…
**Errors encountered**:
| Error | Fix | ~min |
|---|---|---|
| Go not found in container | Downloaded Go binary tarball | 2 |
| NATS server not found | Downloaded nats-server binary | 1 |
| NATS process died after shell exit | Used Python `subprocess.Popen` with `start_new_session=True`…
| `localhost` resolved to IPv6, NATS only on IPv4 | Used `127.0.0.1` explicitly | 1 |
**Verification**: Started both NATS and Resgate. Resgate 1.8.0 logged "Listening on http://0.0.0.0:…

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 4 minutes.
  • Recovered from all 4 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 MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 32 api-gateway projects Argusic has installed and timed, resgate was the 16th fastest to reach a running state, and 22 of 32 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 4 minutes after the clone.

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/3Runs100.000.02

Topics (from GitHub)

api-gatewaygogolangmicroservicesmicroservices-architecturenats-serverrealtimeresgaterest-api

Embed the badge

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

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

Questions

Does resgate run?
Yes. resgate runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test resgate?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0cab702e09ff. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test resgate?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does resgate take to install?
4 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 resgate need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing resgate?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does resgate compare with the alternatives?
Of the 32 api-gateway projects Argusic has installed and timed, resgate was the 16th fastest to reach a running state, and 22 of 32 reached one at all.
Where is the evidence for resgate?
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