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

Workflows manage the orchestration logic and decision-making and must be deterministic, while Activities execute the actual external interactions like API calls or database writes.

Why is determinism important for Temporal workflows?

Temporal uses event sourcing to replay workflow code to recover state; if the code is non-deterministic (e.g., uses random numbers or direct time calls), the replay would result in different states, causing a failure.

When should I use workflow orchestration instead of standard API calls?

Use orchestration for multi-step processes spanning different services, long-running tasks lasting hours to years, and any business process that requires automatic state persistence across system crashes.

How does the Saga pattern work within this skill?

The Saga pattern implements distributed transactions by registering compensating actions before executing steps, allowing for an automated 'rollback' in reverse order if a failure occurs.

Temporal Workflow Orchestration

Name: Temporal Workflow Orchestration
Author: HermeticOrmus

byHermeticOrmus

Despliegue y DevOps

Designs and implements durable, resilient distributed systems using Temporal workflow orchestration patterns and best practices.

Acerca de

This skill provides expert guidance on designing reliable distributed systems with Temporal, focusing on the critical separation between deterministic orchestration logic (Workflows) and non-deterministic external interactions (Activities). It assists developers in implementing complex patterns like Sagas for distributed transactions, entity-based actor models, and parallel execution, while ensuring compliance with strict determinism constraints and robust error handling. Use this skill when building mission-critical backends, multi-step business processes, or microservice orchestrations that must survive infrastructure failures and maintain state over long durations.

Características Principales

Implementation of long-lived entity workflows for stateful object lifecycles
0 GitHub stars
Determinism constraint validation and workflow versioning strategies
Distributed transaction management using the Saga pattern and compensations
Architectural separation of deterministic Workflows and side-effect Activities
Resilience patterns including exponential backoffs, heartbeats, and idempotency

Casos de Uso

Managing long-running human-in-the-loop approval and onboarding workflows
Orchestrating complex multi-step payment and order fulfillment pipelines
Building resilient infrastructure automation and CI/CD provisioning systems

Acerca de

Características Principales

Implementation of long-lived entity workflows for stateful object lifecycles
0 GitHub stars
Determinism constraint validation and workflow versioning strategies
Distributed transaction management using the Saga pattern and compensations
Architectural separation of deterministic Workflows and side-effect Activities
Resilience patterns including exponential backoffs, heartbeats, and idempotency

Casos de Uso

Managing long-running human-in-the-loop approval and onboarding workflows
Orchestrating complex multi-step payment and order fulfillment pipelines
Building resilient infrastructure automation and CI/CD provisioning systems