Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Tasker

Workflow orchestration that meets your code where it lives.

Tasker is an open-source workflow orchestration engine built on PostgreSQL and PGMQ. You define workflows as task templates with ordered steps, implement handlers in Rust, Ruby, Python, or TypeScript, and the engine handles execution, retries, circuit breaking, and observability.

Your existing business logic — API calls, database operations, service integrations — becomes a distributed, event-driven, retryable workflow with minimal ceremony. No DSLs to learn, no framework rewrites. Just thin handler wrappers around code you already have.


Get Started

Getting Started Guide

From zero to your first workflow. Install, write a handler, define a template, submit a task, and watch it run.

Why Tasker?

An honest look at where Tasker fits in the workflow orchestration landscape — and where established tools might be a better choice.

Architecture

How Tasker works under the hood: actors, state machines, event systems, circuit breakers, and the PostgreSQL-native execution model.

Configuration Reference

Complete reference for all 246 configuration parameters across orchestration, workers, and shared settings.


Choose Your Language

Tasker is polyglot from the ground up. The orchestration engine is Rust; workers can be any of four languages, all sharing the same core abstractions expressed idiomatically.

LanguagePackageInstallRegistry
Rusttasker-client / tasker-workercargo add tasker-client tasker-workercrates.io
Rubytasker-rbgem install tasker-rbrubygems.org
Pythontasker-pypip install tasker-pypypi.org
TypeScript@tasker-systems/taskernpm install @tasker-systems/taskernpmjs.com

Each language guide covers installation, handler patterns, testing, and production considerations:

Rust · Ruby · Python · TypeScript


Explore the Documentation

For New Users

Architecture & Design

Operational Guides

Reference

Framework Integrations


Engineering Stories

A progressive-disclosure blog series teaching Tasker concepts through real-world scenarios. Each story follows an engineering team as they adopt workflow orchestration, with working code examples across all four languages.

StoryWhat You’ll Learn
01: E-commerce CheckoutBasic workflows, error handling, retry patterns
02: Data Pipeline ResilienceETL orchestration, resilience under failure
03: Microservices CoordinationCross-service workflows, distributed tracing
04: Team ScalingNamespace isolation, multi-team patterns
05: ObservabilityOpenTelemetry integration, domain events
06: Batch ProcessingBatch step patterns, throughput optimization
07: Conditional WorkflowsDecision handlers, approval flows
08: Production DebuggingDLQ investigation, diagnostics tooling

Stories are being rewritten for the current Tasker architecture. View archive →


The Project

Tasker is open-source software (MIT license) built by an engineer who has spent years designing workflow systems at multiple organizations — and finally had the opportunity to build the one that was always in his head.

It’s not venture-backed. It’s not chasing a market. It’s a labor of love built for the engineering community.

Read the full story →

Source Repositories

RepositoryDescription
tasker-coreRust orchestration engine, polyglot workers, and CLI
tasker-contribFramework integrations and community packages
tasker-bookThis documentation site