workflow-orchestration-patterns

Design durable Temporal workflows with saga, entity, and fan-out/fan-in patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ACGSpgp/ACGS --skill workflow-orchestration-patterns-acgspgp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-orchestration-patterns
Source: https://github.com/ACGSpgp/ACGS/tree/main/.agent/workflows/backend-development/1.2.3/skills/workflow-orchestration-patterns
Command: npx skills add https://github.com/ACGSpgp/ACGS --skill workflow-orchestration-patterns-acgspgp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers design and implement robust, long-running, and fault-tolerant workflows for distributed systems, ensuring reliability and state management in complex microservice architectures.

Core Features & Use Cases

  • Durable Workflows: Design processes that can survive failures and resume automatically.
  • Saga Pattern: Implement distributed transactions with compensation logic for rollback.
  • Entity Workflows: Model long-lived entities with persistent state and event-driven updates.
  • Parallel Execution: Orchestrate multiple tasks concurrently using Fan-Out/Fan-In patterns.
  • Use Case: Orchestrate a multi-step e-commerce order fulfillment process, including inventory checks, payment processing, shipping, and customer notifications, ensuring each step is completed reliably even if services fail.

Quick Start

Use the workflow-orchestration-patterns skill to design a saga pattern for a payment processing workflow.

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?

You implement durable workflows in Temporal by separating non-deterministic business logic into activities and deterministic orchestration into workflows. This separation ensures state persistence and automatic resumption across service failures.

What is the best way to manage state persistence and recovery for long-running workflows?

Temporal entity workflows manage state persistence by modeling long-lived entities with event-driven updates, ensuring durable recovery. This guarantees state survives failures and resumes automatically without data loss.

How do I execute parallel tasks across microservices using a fan-out fan-in pattern?

Temporal orchestrates parallel microservices execution using the fan-out fan-in pattern, dispatching concurrent activities and aggregating results. This ensures reliable parallel task completion across distributed systems.

Do I need to understand workflow determinism constraints to use Temporal for microservices orchestration?

Yes, using Temporal requires understanding workflow determinism constraints. You must separate deterministic workflow logic from non-deterministic activities to ensure reliable microservices orchestration and fault tolerance.

How do I orchestrate a multi-step e-commerce order fulfillment process reliably?

Temporal orchestrates multi-step e-commerce order fulfillment by designing durable workflows for inventory, payments, and shipping. It ensures reliable completion with automatic retries and saga compensation logic.