How does this skill help with distributed transactions?

It provides implementation patterns for the Saga pattern, which ensures that if one step in a distributed sequence fails, the system executes defined compensation logic to roll back previous steps.

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

Workflows handle orchestration logic and decision-making and must remain deterministic. Activities handle external interactions like API calls or database writes and can be non-deterministic.

Why is determinism critical in Temporal workflows?

Temporal recovers state by replaying workflow code against recorded event history. If the code is non-deterministic (e.g., using random numbers or system time), the replay will diverge from history and cause a failure.

When should I avoid using workflow orchestration?

Orchestration engines like Temporal are overkill for simple CRUD operations, stateless request/response APIs, or high-volume real-time data streaming.

Workflow Orchestration Patterns

Name: Workflow Orchestration Patterns
Author: amurata

byamurata

•

Desarrollo de API

Architects resilient distributed systems using Temporal to manage long-running workflows, saga patterns, and deterministic state orchestration.

Acerca de

This skill provides Claude with specialized expertise for designing durable distributed systems using the Temporal orchestration engine. It guides the implementation of reliable backend architectures by enforcing the separation of orchestration logic (Workflows) from side-effect-heavy tasks (Activities). By applying this skill, developers can implement complex patterns like Sagas for distributed transactions, entity-based actor models, and parallel fan-out/fan-in executions. It ensures high system reliability by providing best practices for state persistence, failure recovery, and strict adherence to determinism constraints required for long-running processes.

Características Principales

Enforces the separation of deterministic Workflows and non-deterministic Activities
Configures robust activity retry policies, heartbeats, and idempotency strategies
Provides versioning strategies for updating workflow code without breaking active executions
3 GitHub stars
Implements Saga patterns with automated compensation logic for distributed transactions
Guides the development of long-lived entity workflows for lifecycle management

Casos de Uso

Orchestrating multi-step infrastructure automation and deployment workflows
Managing complex business processes that require human-in-the-loop approvals
Building fault-tolerant payment processing systems and order fulfillment pipelines

Acerca de

Características Principales

Enforces the separation of deterministic Workflows and non-deterministic Activities
Configures robust activity retry policies, heartbeats, and idempotency strategies
Provides versioning strategies for updating workflow code without breaking active executions
3 GitHub stars
Implements Saga patterns with automated compensation logic for distributed transactions
Guides the development of long-lived entity workflows for lifecycle management

Casos de Uso

Orchestrating multi-step infrastructure automation and deployment workflows
Managing complex business processes that require human-in-the-loop approvals
Building fault-tolerant payment processing systems and order fulfillment pipelines