Unified action surface
One button set. Every engine.
z4j commits to a single universal primitive, submit_task, that every engine adapter implements. The brain polyfills retry, bulk-retry, and DLQ-requeue on top of it. The dashboard never disables buttons based on engine.
z4j dashboard — Unified action surface
Mockup of the dashboard view for this feature. Live-reloading and themed to match your dashboard.
Ships with
- Single Protocol method (submit_task) implemented by every adapter
- Brain-side polyfills for retry, bulk-retry, DLQ-requeue
- Dashboard never gates buttons per-engine
- Adding a new engine drops from ~15 methods to ~6
Highlights
- submit_task / cancel_task always native
- retry_task, bulk_retry, requeue_dead_letter polyfilled when absent
- Only restart_worker + rate_limit remain engine-gated (Celery physics)
Related