Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
The 'workflow-orchestration-patterns' skill is designed to help developers and architects create durable workflows using Temporal for distributed systems. It addresses the challenges associated with orchestrating complex processes that span multiple services, databases, and transactions. By leveraging this skill, users can implement workflows that not only preserve state across failures but also ensure that long-running processes can be managed effectively and efficiently, ultimately leading to more robust applications.
Ideal use cases include multi-step processes, distributed transactions, long-running workflows, failure recovery, business processes, entity lifecycle management, infrastructure automation, and human-in-the-loop systems.
Yes, it is not recommended for simple CRUD operations, pure data processing pipelines, stateless request/response scenarios, or real-time streaming.
Workflows contain the orchestration logic and must be deterministic, while activities handle external interactions and can be non-deterministic. Workflows also cannot make direct external calls.
A fundamental rule is to determine if a task touches external systems (then it's an activity) or if it's related to orchestration/decision logic (then it's a workflow).
Compensations must be idempotent, registered before executing the step, run in reverse order on failure, and gracefully handle partial failures.
Quick Setup:
.claude/skills/Repository
wshobson/agents