Taquba

Durable execution for Rust on object storage. Multi-step runs, memoized side effects and background jobs keep their state in a bucket or a local directory, with transactional coordination built in and no database, broker or control plane to operate.

Taquba is a workspace of Rust crates. taquba-workflow runs durable multi-step processes, and taquba is the durable queue underneath it and the substrate of every other crate. Job records, run records and memos are stored in object storage (S3, GCS, Azure Blob or local disk) through SlateDB. Workers do not keep state, so a replacement process resumes where the previous one stopped.

Taquba is embedded and single-process: one process owns each store, and producers and workers share it. It is built for long-running, slow, IO- or API-bound work in one Rust process: LLM agents, batch document pipelines and command-line tools whose runs resume after an interruption. A different tool is the better choice for a worker fleet across machines, a latency-sensitive request path or a high volume of short jobs. The section When to use it, and when not to states…