When should I use workflow orchestration instead of standard APIs?

Use orchestration for processes that span multiple services, require high reliability, need to survive process restarts, or involve long wait times like human approvals or multi-day schedules.

How does this skill help with distributed transactions?

It provides implementation patterns for the Saga Pattern, which allows you to define compensating actions that automatically roll back previous steps if a later step in a distributed process fails.

Why is determinism critical for Temporal workflows?

Temporal uses event replaying to recover workflow state after a crash; if the code is non-deterministic (e.g., using random numbers or direct API calls), the replay would deviate from history and cause a failure.

What is the main difference between a Workflow and an Activity in Temporal?

Workflows handle orchestration logic and must be deterministic (producing the same output for the same input), while Activities handle external interactions like API calls and databases which can be non-deterministic.

Workflow Orchestration Patterns

Name: Workflow Orchestration Patterns
Author: HermeticOrmus

byHermeticOrmus

生産性とワークフロー

Architects resilient, distributed systems using Temporal workflow patterns, saga implementations, and state management best practices.

概要

This skill provides expert guidance for designing and implementing durable workflows using the Temporal framework for complex distributed systems. It helps developers navigate the critical distinction between deterministic orchestration logic (Workflows) and non-deterministic external interactions (Activities), while implementing complex patterns like Sagas for distributed transactions and Entity Workflows for long-lived state management. By enforcing best practices around idempotency, error handling, and versioning, this skill ensures that distributed processes remain resilient, recoverable, and maintainable even across long-running timelines or infrastructure failures.

主な機能

Implementation patterns for the Saga Pattern with automated compensation logic
Architectural blueprints for Entity Workflows and parallel Fan-Out/Fan-In execution
0 GitHub stars
Best practices for idempotent Activity design and failure recovery strategies
Strategies for workflow versioning and backward compatibility in production
Guidance on maintaining workflow determinism and avoiding non-deterministic traps

ユースケース

Orchestrating complex microservice interactions requiring distributed transaction semantics
Building multi-step payment and order fulfillment pipelines with automatic error recovery
Managing long-lived entity lifecycles such as subscription billing or user account state

概要

主な機能

Implementation patterns for the Saga Pattern with automated compensation logic
Architectural blueprints for Entity Workflows and parallel Fan-Out/Fan-In execution
0 GitHub stars
Best practices for idempotent Activity design and failure recovery strategies
Strategies for workflow versioning and backward compatibility in production
Guidance on maintaining workflow determinism and avoiding non-deterministic traps

ユースケース

Orchestrating complex microservice interactions requiring distributed transaction semantics
Building multi-step payment and order fulfillment pipelines with automatic error recovery
Managing long-lived entity lifecycles such as subscription billing or user account state