Tork is a lightweight, distributed workflow engine that runs tasks as simple scripts within Docker containers.
-
Updated
Jul 21, 2026 - Go
Tork is a lightweight, distributed workflow engine that runs tasks as simple scripts within Docker containers.
⏳ Durable step functions via Postgres.
auto-scaling worker pool (work queue) in Go, using generics
Microsecond message queues over HTTP and raw TCP — one static binary, zero dependencies, nothing to operate.
NodeJS library to work with FoundationDB
MutexGear Library Preview
Command-line task queue
A boringly-named priority work queue system for doing async tasks.
A durable, simple, opinionated, transactional work queue offering many features of a messaging system.
A simple PHP library for work-queue and job handling.
CLI-native state persistence for AI agents — tasks, memory, state, and queues. One binary per primitive. No setup. No infrastructure.
A durable work queue that is one database table. Optimistic locking, no broker, no dependencies. A template you copy, not a library you depend on.
Use email as an async durable work-queue/backend for your static website or w/e else you want. It's like a trigger for a serverless function but even more serverless than the cloud providers can offer!
A fast job queue server with unique jobs, concurrency controls, and job group pipelines. One binary, zero dependencies.
Generic, durable, FIFO disk-backed queue for Go — a persistent work queue that doubles as a write-ahead log. Zero-alloc hot paths, one dependency.
An AMQP adapter for WQ (https://github.com/mle86/php-wq)
A Redis adapter for WQ (https://github.com/mle86/php-wq)
From-scratch TypeScript message broker: pub/sub, topic patterns, dead-letter queues, and the delivery semantics behind Kafka, RabbitMQ, and SQS.
Distributed job orchestrator in Go: fenced leases with monotonic generations, DAG dependencies, deficit round-robin fairness, and a SQLite control plane whose scheduler decisions replay byte for byte, with a chaos and reconciliation harness that voids its own runs rather than publishing an ambiguous number.
Add a description, image, and links to the work-queue topic page so that developers can more easily learn about it.
To associate your repository with the work-queue topic, visit your repo's landing page and select "manage topics."