Can I use standard Rust async timers?

No, standard timers like tokio::time::sleep break determinism. You must use the provided context methods like ctx.schedule_timer for durable execution.

How are activities different from orchestrations in Duroxide?

Activities perform the actual side effects (like database writes or API calls) and must be idempotent, while orchestrations coordinate these activities using deterministic logic.

Why use Duroxide with Claude Code?

This skill guides Claude to write code that adheres to strict determinism requirements, ensuring workflows don't break during history replay.

What is a durable workflow?

A durable workflow is a process that can survive system failures or restarts by recording its execution history and replaying it to restore state deterministically.

What is the 'Continue-as-new' pattern?

It is a pattern used to prevent execution history from growing too large by restarting the workflow with a clean history while passing the current state forward.

Duroxide Workflow Orchestrations

Name: Duroxide Workflow Orchestrations
Author: affandar

byaffandar

API Development

Builds deterministic, fault-tolerant workflows in Rust using the Duroxide orchestration engine.

About

This skill empowers developers to build complex, multi-step business logic that remains resilient against system failures and restarts. By leveraging Duroxide's replayable orchestration model, it enables the creation of activities and workflows with built-in idempotency, automatic retries, and deterministic execution history. It is specifically designed for high-reliability systems like cloud control planes where state consistency and recovery are critical.

Key Features

Deterministic timers and signal handling for asynchronous event coordination
Hierarchical naming conventions and centralized registry management
Deterministic orchestration logic for reliable workflow execution
Advanced patterns like Sub-orchestrations and Continue-as-new for long-running tasks
Fault-tolerant activities with customizable retry policies and backoff strategies
0 GitHub stars

Use Cases

Coordinating complex multi-step API operations requiring high consistency
Building managed service control planes for database provisioning
Managing long-running background tasks with external system interactions

About

Key Features

Deterministic timers and signal handling for asynchronous event coordination
Hierarchical naming conventions and centralized registry management
Deterministic orchestration logic for reliable workflow execution
Advanced patterns like Sub-orchestrations and Continue-as-new for long-running tasks
Fault-tolerant activities with customizable retry policies and backoff strategies
0 GitHub stars

Use Cases

Coordinating complex multi-step API operations requiring high consistency
Building managed service control planes for database provisioning
Managing long-running background tasks with external system interactions