pikku-workflow

You can orchestrate durable multi-step workflows in a Pikku application by using pikkuWorkflowFunc and pikkuWorkflowGraph to model sequential steps and graph DAGs with built-in retries and execution state management.

Durable execution persists the state of multi-step workflows, allowing them to survive failures and resume seamlessly. You need it when orchestrating complex processes like user signups that require reliable validation, email, and data persistence across services.

Yes, you can suspend a Pikku workflow and resume it later. The Skill provides HTTP wiring to integrate external triggers and status checks, allowing workflows to suspend execution and wait for external events or responses.

You build a DAG workflow graph by using pikkuWorkflowGraph to define complex dependencies, combined with do, sleep, and suspend step controls to manage execution flow and apply automatic retries for failed operations.

Yes, it integrates directly with existing Pikku services through HTTP wiring. This allows you to attach durable workflows to current HTTP endpoints, enabling external triggers and status checks without replacing your application architecture.

Graph DAGs require explicitly defined dependencies between steps, meaning circular dependencies are unsupported. While durable execution handles retries and state persistence, complex conditional branching beyond the defined graph structure may need manual state management.