liftbridge

Kafka-style message streaming in Go. Built on NATS. Single binary, no JVM, no ZooKeeper.

Runs with mockssource: GitHubhomepageGoApache-2.0commit af2a662695ce

Go, Apache-2.0 licensed. The project labels itself: cloud native, distributed systems, go, golang, grpc, liftbridge, message queue and messaging.

liftbridge runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Liftbridge binary builds and launches with embedded NATS; 5 of 6 test packages pass (59 sub-tests), the integration test suite needs gRPC infrastructure unavailable in 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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.45 (measured)
recorded runs
2
last tested
stars
2,805
forks
117
open issues
47
watchers
59
size
17 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 liftbridge, 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.

  • Build error: `http2.TrailerPrefix` undefined in grpc handler_server.go on Go 1.275 minutes
  • go command not found in container2 minutes
  • nats-server binary not available (no apt/sudo)
  • server_test.go integration tests fail silently (TestActivityStreamCreateStream hangs/timeouts)
Install time
12 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
`go test -tags http2legacy github.com/liftbridge-io/liftbridge/server/commitlog` and 4 other sub-packages all passed; `timeout 6 ./liftbridge --config /tmp/lb-test.yaml` printed startup logs through 'Telemetry sent successfully' then exited 0
Model tokens used
160,337
Exact commit tested
af2a662695ce
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
Behaviour against real services
this run was verified against stand-in services only

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 2, 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.

- Ran all sub-package tests (commitlog, health, logger, protocol, telemetry) — all pass
- Verified the server launches with embedded NATS and processes startup lifecycle
- The top-level `server_test.go` integration tests need gRPC/embedded NATS resources not available …
tokens used
160,337
Now I have all the information needed. Let me compile the results:
**Summary of work done:**
- Installed Go 1.27.4 from go.dev (required by project specifies Go ≥1.25.6)
- Built the Liftbridge binary with the `http2legacy` build tag fix for Go 1.27+ compatibility
- Ran all sub-package tests (commitlog, health, logger, protocol, telemetry) — all pass
- Verified the server launches with embedded NATS and processes startup lifecycle
- The top-level `server_test.go` integration tests need gRPC/embedded NATS resources not available …

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

  • Installed in 12 minutes, faster than the median of the 4 comparable projects Argusic has measured.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 5 cloud-native projects Argusic has installed and timed, liftbridge was the 2nd fastest to reach a running state, and 3 of 5 reached one at all.

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.45
Argusic Runner1/3Runs with mocks92.000.12

Topics (from GitHub)

cloud-nativedistributed-systemsgogolanggrpcliftbridgemessage-queuemessagingnatspubsubstreaming

Embed the badge

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

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

Questions

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