russellromney/honker
SQLite extension + bindings for Postgres NOTIFY/LISTEN semantics with durable queues, streams, pub/sub, and scheduler observed · 2026-08-28
Health v2 · maintenance only
81/100
- Activity 99
- Release rhythm 99
- Longevity 9
Flags: young no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 1
- age_days: 137
- days_rel: 7
- days_push: 7
- n_releases_24m: 4
Adoption not part of the score
3015 stars · 75 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A SQLite loadable extension plus multi-language bindings that add Postgres-style NOTIFY/LISTEN semantics, durable task queues, event streams, pub/sub, and cron scheduling directly inside a SQLite database file. It enables transactional outbox patterns where business writes and job enqueues commit atomically, without needing Redis, Celery, or any external broker.
Use cases
- add a durable background job queue to a SQLite-backed app without running Redis or Celery
- implement the transactional outbox pattern so business inserts and enqueued jobs commit or roll back together
- send cross-process notifications between workers sharing one SQLite file
- build durable event streams with per-consumer offsets that resume after crashes
- schedule recurring tasks with cron or @every expressions from a SQLite database
- enqueue work in one language and consume it in another via shared on-disk format
- replace polling-based queue tables with push-like low-latency wakeups
When to choose
- SQLite is your primary datastore and you need queues, pub/sub, or scheduling without adding a second datastore or broker
- you want atomic enqueue with business writes in the same transaction
- you need cross-language workers sharing the same queue file
- you want single-digit-millisecond cross-process wake latency with zero infrastructure
When to avoid
- you need workflow DAGs, task chains, groups, or chords (explicitly out of scope)
- you need multi-writer replication or distributed locking across machines
- your workload requires a networked message broker or multi-node fan-out
- you need beta-quality or stable software (it is alpha)
Facets
library · maturity experimental
message-queue database scheduling caching concurrency databases backend developer-tools python rust go ruby jvm dotnet cpp elixir cross-platform cli sqlite-extension notify-listen task-queue pubsub event-streams transactional-outbox cron-scheduler dead-letter bindings no-broker messaging automation nodejs
4 sources
- readme: https://github.com/russellromney/honker · fetched 2026-08-28 · 82e8f040516f
- homepage: https://honker.dev · fetched 2026-08-29 · e9cdf5c52eee
- site_page: https://honker.dev/docs · fetched 2026-08-29 · 8f41c5188976
- registry_pypi: https://pypi.org/pypi/honker/json · fetched 2026-08-29 · d0c480604182
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| russellromney/honker | main | 81 |
For agents
markdown · JSON · MCP: product_card(name="russellromney/honker")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem