spring-cloud-gateway

An API Gateway built on Spring Framework and Spring Boot providing routing and more.

Runssource: GitHubhomepageJavaApache-2.0commit 88a92c065767

Java, Apache-2.0 licensed. The project labels itself: api gateway, java, microservices, proxy, reactor, spring, spring boot and spring cloud.

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

Spring Cloud Gateway builds fully from source; the WebFlux server module passes 791 tests with 0 failures and 0 errors; WebMVC module fails integration tests requiring Docker, and Docker-dependent integration tests are correctly excluded via the withoutDockerTests profile.

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.22 (measured)
recorded runs
2
last tested
stars
4,920
forks
3,483
open issues
586
watchers
206
size
16 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 spring-cloud-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.

  • StreamRoutingFilterTests uses Testcontainers (RabbitMQ) but lacks @Tag("DockerRequired"), causing container fetch error4 minutes
  • All 19 WebMVC test classes use HttpbinTestcontainers requiring Docker, causing 105 test errors2 minutes
  • No Java JDK found in container1 minute
Install time
8 minutes
Cold machine to finish
69 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
./mvnw test -P withoutDockerTests -pl spring-cloud-gateway-server-webflux: 791 run, 0 failures, 0 errors, 8 skipped. ./mvnw install -DskipTests: BUILD SUCCESS across all 15 modules.
Model tokens used
190,582
Exact commit tested
88a92c065767
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.

**Error 1: No Java JDK installed**
- Fixed: Downloaded Adoptium Temurin JDK 17.0.1+12, extracted to `/tmp/jdk-17.0.1+12`, set `JAVA_HO…
**Error 2: `StreamRoutingFilterTests` requires Docker but isn't tagged `@Tag("DockerRequired")`**
- Fixed: Added the `@Tag("DockerRequired")` annotation and the corresponding import to `StreamRouti…
**Error 3: WebMVC tests all use `HttpbinTestcontainers` and fail without Docker**
- Not fixable without Docker. 105 errors in 19 test files.
**Build results:**
- `./mvnw install -DskipTests`: **BUILD SUCCESS** (all 15 modules)
- `spring-cloud-gateway-server-webflux` tests (`-P withoutDockerTests`): **791 run, 0 failures, 0 e…
- `spring-cloud-gateway-proxyexchange-webflux` + `-webmvc` tests: **34 run, 0 failures, 0 errors, 0…
- `spring-cloud-gateway-sample` + starters: **13 run, 0 failures, 0 errors, 0 skipped**
- `spring-cloud-gateway-server-webmvc` tests: **216 run, 0 failures, 105 errors** (all Docker integ…

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 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 did not, or is not known

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

Of the 32 api-gateway projects Argusic has installed and timed, spring-cloud-gateway was the 19th 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 8 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 Runner2/3Ran out of time0.000.29
Argusic Runner1/3Runs100.000.22

Topics (from GitHub)

api-gatewayjavamicroservicesproxyreactorspringspring-bootspring-cloudspring-cloud-core

Embed the badge

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

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

Questions

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