RQ
v1.0z4j-rq · Upstream project
Lightweight Redis queue, fully instrumented.
RQ's worker model has no remote-control channel, but every data-plane action is implemented: retry, cancel, bulk retry, purge, requeue-dead-letter, plus worker-wrap event capture.
Install
pip install z4j-rqNative actions
-
submit_task -
retry_task -
cancel_task -
bulk_retry -
purge_queue -
requeue_dead_letter
Not supported
- restart_worker (graceful self-exit instead)
- rate_limit
Engine-level limitations, not a roadmap gap. These actions require primitives the engine does not expose.
Wiring
How z4j plugs in
Event capture
Worker-wrap monkey-patch plus per-job callbacks. No code changes required in your jobs.
Reconciliation
rq.job.Job: status + ended_at + exc_info from the Redis hash.
Paired scheduler
rq-scheduler
RQ's optional scheduler, wired to the dashboard.
z4j-rqscheduler
Wraps rq-scheduler's Redis sorted-set scheduler. v1 ships read + lifecycle operations; programmatic schedule creation lands in v1.1.
Learn more More engines
