varmq

A Simplest Storage-Agnostic and Zero-dep Message Queue for Your Concurrent Go Program

Not yet testedsource: GitHubhomepageGoMITcommit 1f9d9b588f73

Go, MIT licensed. The project labels itself: concurrency, distrubted systems, go, goroutine, goroutine pool, hacktoberfest, message queue and persistence.

varmq has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
208
forks
19
open issues
10
watchers
2
size
6 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.

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

No recorded runs.

Topics (from GitHub)

concurrencydistrubted-systemsgogoroutinegoroutine-poolhacktoberfestmessage-queuepersistencepoolpriority-queuequeuevarmqworkerworker-pool

Embed the badge

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

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

Questions

Does varmq run?
varmq has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test varmq?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for varmq?
All 0 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