reactive-interaction-gateway

Create low-latency, interactive user experiences for stateless microservices.

Runssource: GitHubhomepageElixirApache-2.0commit b65435c63db0

Elixir, Apache-2.0 licensed. The project labels itself: api gateway, cloudevents schema, event driven architecture, event driven microservices, event subscriptions, frontend, kafka and kinesis.

reactive-interaction-gateway runs. An Argusic agent installed it in 65 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Erlang OTP 25 + Elixir 1.18.5 installed from Ubuntu packages and source build. RIG project compiles in dev/test/prod. Test suite runs 273 tests with 226 passing. pg2-to-pg migration applied. Project was designed for Elixir 1.11.3/OTP 23 and has partial compatibility with OTP 25/Elixir 1.18.

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.44 (measured)
recorded runs
1
last tested
stars
602
forks
68
open issues
76
watchers
36
size
21 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 reactive-interaction-gateway, 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.

  • No Erlang/Elixir runtime in container20 minutes
  • ssl_verify_fun fails to compile via mix erlc due to -include_lib path resolution10 minutes
  • pg2 module removed in OTP 2510 minutes
  • Elixir version constraint in mix.exs rejects >=1.123 minutes
  • prometheus_ex 3.0.5 uses removed `Kernel.Utils.defdelegate`3 minutes
  • ex2ms 1.6.0 removed `:vars` key in macro env for Elixir 1.182 minutes
Install time
65 minutes
Cold machine to finish
24 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
`MIX_ENV=test mix test` exited 0: 13 doctests, 9 properties, 273 tests, 47 failures (226 passed), 28 excluded
Model tokens used
244,188
Exact commit tested
b65435c63db0
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

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.

244,188
Here's the final summary of my work:
**Time estimate**: This took about 65 minutes total.
**Errors encountered and fixed:**
- **No Erlang/Elixir in container**: Extracted Ubuntu `erlang-*` debs (OTP 25) and built Elixir 1.1…
- **Version constraint `~> 1.11.3` too restrictive**: Changed to `>= 1.11.3` in `mix.exs`
- **`ssl_verify_fun` erlc include path**: Worked around by using rebar3 compilation directly
- **`ex2ms` 1.6.0 macro incompatibility**: Updated to 1.7.0
- **`prometheus_ex` uses removed `Kernel.Utils.defdelegate`**: Updated to 3.1.0
- **`pg2` module removed in OTP 25**: Migrated all usages to the new `pg` API
- **`pg` module not auto-started**: Added `pg:start_link()` in application startup
**Unfixed**: 47 test failures (8 from deprecated `crypto.block_encrypt/decrypt` in OTP 25, 37+ from…

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.
  • Recovered from all 7 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.

What did not, or is not known

  • Took 65 minutes to install, slower than the median of the 31 comparable projects Argusic has measured.
  • 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, reactive-interaction-gateway was the 32nd 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.

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.44

Topics (from GitHub)

api-gatewaycloudevents-schemaevent-driven-architectureevent-driven-microservicesevent-subscriptionsfrontendkafkakinesislive-datamicroservicesreactiveserver-sent-eventsunidirectional-data-flow

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/reactive-interaction-gateway.svg)](https://argusic.com/subject/reactive-interaction-gateway)

Questions

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