Durable Workflow keeps long-running application code moving through process
restarts, retries, timers, and human input. Workflows and activities are written
in ordinary application code while the runtime records history and resumes work
without repeating completed steps.
The SDKs share workflow and activity type names, task queues, namespaces, and a
portable Avro value protocol. A workflow in one language can dispatch an
activity to a worker in another.
Runtime capabilities
Durable workflows and activities with retries, timeouts, and heartbeats
Timers, schedules, signals, queries, and updates
Child workflows, sagas, cancellation, and continue-as-new
Namespaces, search attributes, memo, and workflow history
Durable Workflow is created and maintained by Richard McDaniel (@rmcdaniel), who is also responsible for security maintenance, vulnerability triage, and security fixes across the project.
Language-neutral workflow orchestration server for running durable workflows with external workers over HTTP. Supports task polling, schedules, namespaces, history export, role-scoped auth, and Docker/Compose/Kubernetes deployment, with persistence backed by SQLite, MySQL, or PostgreSQL.
Core package for defining and running durable workflows and activities. Supports long-running persistent workflows, retries, queues, parallel execution, workflow monitoring, dedicated storage connections, and orchestration for microservices, data pipelines, sagas, agentic workflows, and other complex business processes.
Documentation website for Durable Workflow, built with Docusaurus and published at durable-workflow.com. Hosts versioned product docs, guides, blog content, compatibility information, migration resources, and public documentation checks for the Durable Workflow ecosystem.
There was an error while loading. Please reload this page.
Most used topics
Loading…
Uh oh!
There was an error while loading. Please reload this page.
You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.