workflow-orchestration-patterns

Design durable Temporal workflow orchestrations with Saga, fan-out, and retry patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rawhit-r/ai-files --skill workflow-orchestration-patterns-rawhit-r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-orchestration-patterns
Source: https://github.com/rawhit-r/ai-files/tree/main/.gemini/workflow-orchestration-patterns
Command: npx skills add https://github.com/rawhit-r/ai-files --skill workflow-orchestration-patterns-rawhit-r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and implement durable, deterministic workflow orchestration for distributed systems using Temporal, covering choices between workflows and activities, state management, and resilience patterns.

Core Features & Use Cases

  • Covers Saga patterns with compensation, entity-centric workflows (actor model), fan-out/fan-in parallel execution, and async callback patterns.
  • Emphasizes determinism, idempotency, automatic state preservation, retry strategies, and heartbeat mechanisms for long-running tasks.
  • Real-world use cases include long-running order processing, inventory and payments coordination, and multi-service orchestration with reliable recovery.

Quick Start

Describe a durable workflow architecture for a long-running order processing scenario using Temporal patterns.

Frequently Asked Questions about workflow-orchestration-patterns

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

FAQPage Schema
How do I design a durable workflow for long-running order processing in distributed systems?

Design a durable workflow by leveraging Temporal for automatic state preservation, deterministic execution, and compensation patterns like Saga to coordinate multi-step order processing across microservices with reliable recovery.

What is the Saga pattern in workflow orchestration and when should I use it?

The Saga pattern in workflow orchestration handles multi-step business processes by defining compensation logic for each step. Use it when coordinating transactions across microservices that require reliable rollback mechanisms upon partial failures.

How do I ensure determinism and idempotency in Temporal activities?

Ensure determinism by keeping workflow logic free of non-deterministic operations, and guarantee idempotent activities by designing them to safely handle duplicate executions during automatic retries and state recovery.

Can I use fan-out fan-in parallel execution for microservice orchestration?

Yes, you can use fan-out fan-in parallel execution for microservice orchestration. This workflow pattern distributes concurrent tasks across multiple services and aggregates results, optimizing throughput for distributed processing.

What's the best way to handle retries and heartbeats for long-running tasks in workflow orchestration?

Handle retries and heartbeats for long-running tasks by configuring robust retry strategies and implementing heartbeat mechanisms. This ensures the orchestration engine tracks activity progress and recovers reliably from transient failures.

When should I choose entity-centric workflows over standard orchestration patterns?

Choose entity-centric workflows, utilizing an actor model approach, when you need to encapsulate business logic and state around specific domain entities. This pattern provides isolated state management for durable, long-running processes.