scalecube-services
Microservices library - scalecube-services is a high throughput, low latency reactive microservices library built to scale. It features: API-Gateways, service-discovery, service-load-balancing, the architecture supports plug-and-play service communication modules and features. built to provide performance and low-latency real-time stream-processing
Runssource: GitHubhomepageJavaApache-2.0commit 76d941b9df18
Java, Apache-2.0 licensed. The project labels itself: actor model, aeron, api gateway, backpressure, cluster, cluster membership, distributed systems and gossip protocol.
scalecube-services runs. An Argusic agent installed it in 10.1 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
scalecube-services builds successfully with Maven; 373/374 tests pass across all modules except services-security which requires Docker for Vault Testcontainers integration tests
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 80 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- services-security: ServiceTokenTests fails because Docker socket unavailable (Testcontainers Vault container)0.5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- mvn test ran 374 tests across 9 modules; 373 passed, 0 failures, 7 skipped, 1 error (security module needs Docker)
- Model tokens used
- 446,097
- Exact commit tested
- 76d941b9df18
- 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.
## Summary I downloaded **JDK 17 (Temurin)** and **Maven 3.9.6** to your home directory, then built and tested… **Build:** ✅ All 10 modules compiled successfully via `mvn install -DskipTests`. **Tests:** ✅ 373/374 pass across 9 testable modules. The only error is in `services-security/Servic… - 6 modules had no issues - `services-api`: 75 tests, all pass - `services-discovery`: 4 tests, 2 skipped, all pass - `services-gateway`: 119 tests, all pass - `services-transport-rsocket`: 5 tests, all pass - `services`: 159 tests, 5 skipped, all pass - `services-security`: 1 test error (Docker) No code changes were needed to make the build succeed.
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 10.1 minutes.
- 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
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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
Topics (from GitHub)
actor-modelaeronapi-gatewaybackpressureclustercluster-membershipdistributed-systemsgossip-protocolipck8slow-latencymicroservicesmulticast-streamsreactive-microservicesreactive-streamsreactor-aeronreactor-nettyservice-discoveryservice-meshswim-protocol
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scalecube-services)Questions
- Does scalecube-services run?
- Yes. scalecube-services runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test scalecube-services?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 76d941b9df18. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test scalecube-services?
- 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 scalecube-services take to install?
- 10.1 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 scalecube-services need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing scalecube-services?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for scalecube-services?
- 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.