gisila_queue 0.1.0

A Celery-like distributed task queue for Dart: register named tasks, enqueue them from anywhere with .delay()/.applyAsync(), and process them with worker pools backed by a pluggable broker (Redis or i [...]

Changelog

Unreleased

• Observability layer (opt-in). Producers and workers now emit lifecycle QueueEvents to an optional QueueEventSink on GisilaQueue (defaults to a zero-overhead NoopEventSink):
  • Sinks/sources: InMemoryEventBus (single isolate), RedisEventSink / RedisEventSource (pub/sub + capped history), MultiEventSink.
  • Workers report a stable id, periodic heartbeats, and per-outcome events.
• GisilaRose — an optional web dashboard (package:gisila_queue/gisila_rose.dart) for live tasks, workers, and queue depths, with a JSON API and SSE live tail. Run standalone via dart run gisila_queue:rose. The analogue of Celery's Flower.

0.1.0

Initial release.

• GisilaQueue app with a named-task registry and typed TaskRef producers (.delay() / .applyAsync()).
• Pluggable Broker: InMemoryBroker (single-isolate / tests) and RedisBroker (distributed, list-based queues + sorted-set ETA scheduling).
• Pluggable ResultBackend: InMemoryResultBackend and RedisResultBackend (TTL'd result keys); backend is optional for fire-and-forget use.
• Worker with cooperative async concurrency, named-queue priority routing, retries with exponential backoff + jitter, ctx.retry() / RejectTask, and success/failure/retry observer hooks.
• AsyncResult for polling task state and awaiting return values.
• Beat scheduler for periodic tasks (Schedule.every, Schedule.dailyAt).