Dramatiq
v1.0z4j-dramatiq · Upstream project
Middleware-driven Dramatiq observability.
Ships as a single Z4JMiddleware with no monkey-patching. Dual broker support on day one (Redis + RabbitMQ). Abortable-gated cancel promoted into capabilities only when the middleware is installed.
Install
pip install z4j-dramatiqNative actions
-
submit_task -
retry_task -
cancel_task (Abortable-gated) -
purge_queue -
bulk_retry -
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
Z4JMiddleware, Dramatiq's blessed observability hook.
Reconciliation
Results middleware (when configured). Reads back stored results; falls through to unknown otherwise.
Paired scheduler
APScheduler
Engine-agnostic scheduler. Pair with anything.
z4j-apscheduler
APScheduler is the best fit when you want one process to drive Dramatiq schedules (or any engine without a native scheduler).
Learn more More engines
