wellle/rmq
Message queue system written in Go and backed by Redis observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4028
- days_rel: n/a
- days_push: 628
- n_releases_24m: 0
Adoption not part of the score
1617 stars · 207 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
rmq is a message queue library for Go backed by Redis, supporting connections, queues, consumers, batching, and Redis clusters. It lets Go services enqueue and consume tasks asynchronously using Redis as the storage layer.
Use cases
- enqueue background jobs from a Go service
- process tasks asynchronously with worker consumers
- build a lightweight job queue without RabbitMQ or Kafka
- distribute work across multiple Go workers via Redis
- queue and batch-deliver events backed by Redis
- monitor queue statistics for a Go application
When to choose
- you already run Redis and want a simple Go-native message queue
- you need lightweight background job processing without heavyweight broker infrastructure
- you want queue statistics, batching, and consumer management from a Go library
When to avoid
- you need guaranteed delivery, complex routing, or AMQP features
- you don't want a Redis dependency
- you need a distributed queue across datacenters with strong ordering guarantees
Facets
library · maturity active
message-queue caching backend developer-tools go windows redis-backed task-queue background-jobs go-library messaging redis linux macos
1 source
- readme: https://github.com/wellle/rmq · fetched 2026-08-28 · 05bbb9c996ec
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| wellle/rmq | main | 23 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem