spring-cloud-stream

Framework for building Event-Driven Microservices

Runssource: GitHubhomepageJavaApache-2.0commit 4d7cce1b2761

Java, Apache-2.0 licensed. The project labels itself: cloud native, event driven microservices, messaging, microservices, reactive and stream processing.

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

Spring Cloud Stream 5.1.0-SNAPSHOT compiles, installs and passes 958 tests (0 failures) across core, kafka, kafka-streams, pulsar and schema-registry modules; a real RabbitMQ 3.12.1 broker runs locally and serves AMQP and its management API; only the Rabbit binder integration suite cannot run because its Testcontainers harness requires a Docker daemon absent from 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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
2
last tested
stars
1,071
forks
657
open issues
124
watchers
76
size
22 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-stream, 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.

  • mvn test on spring-cloud-stream-binder-rabbit failed: Testcontainers RabbitTestContainer requires a Docker daemon (Could not find a valid Docker environment); Docker cannot be installed here (no root, no newuidmap/slirp4netns, no docker socket)18 minutes
  • No system packages can be installed (no root); Erlang asn1 app initially missing from extracted tree10 minutes
  • No JDK or Maven present in container; downloaded user-space Temurin JDK 17 and Maven 3.9.9 to ~/tools8 minutes
  • mvn install for the Rabbit binder module has no external-broker env switch (test harness hard-wires org.testcontainers.containers.RabbitMQContainer static init), so that module suite cannot run without Docker5 minutes
Install time
61 minutes
Cold machine to finish
62 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
mvn install -Dstyle.color=never -pl '!binders/rabbit-binder/spring-cloud-stream-binder-rabbit' exited 0, BUILD SUCCESS, 958 tests run 0 failures 110 skipped; java AMQP client against localhost:5672 printed 'AMQP_OK received=hello'; curl -u guest:guest http://127.0.0.1:15672/api/overview returned 200
Model tokens used
1,698,576
Exact commit tested
4d7cce1b2761
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.

- No JDK/Maven in container → downloaded user-space Temurin JDK 17 + Maven 3.9.9 to `~/tools` (no r…
- `./mvnw install` (README's documented command) failed only at `spring-cloud-stream-binder-rabbit`…
- To bridge, I booted a **real RabbitMQ 3.12.1 broker** in user-space (downloaded Ubuntu .debs, ext…
  - `mvn install` excluding only that module → **BUILD SUCCESS**, 25/25 modules.
  - Test aggregates across all runnable modules: **958 tests, 0 failures, 110 skipped** (skips are …
- Final state: all artifacts installed into `~/.m2`, core jar built, broker still running.
exec
/bin/sh -lc 'curl -s -u guest:guest http://127.0.0.1:15672/api/overview >/dev/null && echo "final c…
 succeeded in 0ms:
final check: mgmt api 200 OK
tokens used
1,698,576

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 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 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 61 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 cloud-native projects Argusic has installed and timed, spring-cloud-stream was the 5th fastest to reach a running state, and 3 of 5 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 Runner2/3Runs with mocks92.000.46
Argusic Runner1/3Runs100.000.44

Topics (from GitHub)

cloud-nativeevent-driven-microservicesmessagingmicroservicesreactivestream-processing

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-stream.svg)](https://argusic.com/subject/spring-cloud-stream)

Questions

Does spring-cloud-stream run?
Yes. spring-cloud-stream runs. Argusic installed and launched it on a clean machine in 61 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test spring-cloud-stream?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4d7cce1b2761. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test spring-cloud-stream?
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 spring-cloud-stream take to install?
61 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-stream need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing spring-cloud-stream?
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 spring-cloud-stream compare with the alternatives?
Of the 5 cloud-native projects Argusic has installed and timed, spring-cloud-stream was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
Where is the evidence for spring-cloud-stream?
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