workflow-orchestration-patterns

...

2|Updated Feb 5, 2026

Search Tags:#state management #workflow orchestration #resilience #distributed systems #temporal #saga pattern

Ready to run

npx skills add https://github.com/yashvinthan/DuskSpendr --skill workflow-orchestration-patterns-yashvinthan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-orchestration-patterns
Source: https://github.com/yashvinthan/DuskSpendr/tree/main/.agents/skills/workflow-orchestration-patterns
Command: npx skills add https://github.com/yashvinthan/DuskSpendr --skill workflow-orchestration-patterns-yashvinthan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of building reliable, long-running, and distributed systems by providing patterns and best practices for workflow orchestration using Temporal.

Core Features & Use Cases

Durable Workflows: Design and implement workflows that can survive infrastructure failures and resume automatically.
Saga Pattern: Manage distributed transactions with compensation logic for eventual consistency.
Entity Workflows: Model long-lived entities as workflows for state management and event-driven updates.
Parallel Execution: Efficiently run multiple tasks concurrently using fan-out/fan-in patterns.
Use Case: Orchestrating a multi-step e-commerce order process, including inventory checks, payment processing, and shipping, ensuring all steps are completed or properly compensated for in case of failures.

Quick Start

Use the workflow-orchestration-patterns skill to design a saga pattern for a distributed order placement system.

Frequently Asked Questions about workflow-orchestration-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement the saga pattern for distributed transactions in microservices?▼

The saga pattern manages distributed transactions by defining compensation logic for each step, ensuring eventual consistency. You structure workflows to execute forward and compensate backward automatically upon failures, maintaining reliable state across microservices.

What is the best way to build durable workflows that survive infrastructure failures?▼

Durable workflows persist their execution state automatically, allowing them to resume from the exact point of failure after an infrastructure crash. You separate business logic into workflows and side-effect tasks into activities to guarantee deterministic replay.

How do I handle state management for long-running processes in distributed systems?▼

State management for long-running processes is handled by modeling them as entity workflows. This approach encapsulates state and behavior within a long-lived workflow, processing event-driven updates while maintaining durability and consistency.

How does fan-out fan-in parallel execution work for workflow orchestration?▼

Fan-out fan-in parallel execution dispatches multiple activity tasks concurrently from a workflow and aggregates their results upon completion. This pattern maximizes throughput for independent operations while the orchestration engine handles retries and state persistence.

What are the determinism constraints when designing workflows in Temporal?▼

Workflow determinism constraints require that workflow code produces the exact same sequence of commands upon replay. You must isolate non-deterministic operations like API calls or database access into activities, keeping the workflow logic purely functional.

When do I need workflow orchestration for distributed systems instead of standard API calls?▼

Workflow orchestration is needed for distributed systems when processes are long-running, require multi-step transactions, or demand guaranteed completion despite failures. It replaces standard API calls with durable execution, saga rollbacks, and automatic state recovery.