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

Workflows contain the orchestration logic and must be deterministic to allow for state replay, while Activities handle external interactions like API calls and can be non-deterministic.

How does this skill handle distributed transactions?

It implements the Saga Pattern, which registers compensation actions for every successful step to ensure that the system can rollback to a consistent state if a later step fails.

When should I use workflow orchestration instead of standard APIs?

Use orchestration for multi-step processes spanning different services, long-running tasks requiring state persistence, or processes that need automatic failure recovery.

Why is determinism critical for Temporal workflows?

Temporal recovers state by replaying code against an event history; if the code is non-deterministic (using random numbers or system time), the replay would diverge and fail.

Workflow Orchestration Patterns

Name: Workflow Orchestration Patterns
Author: Microck

byMicrock

•

Infraestructura en la Nube

Designs durable, resilient distributed system workflows using Temporal orchestration patterns and industry best practices.

Acerca de

This skill provides specialized architectural guidance for building reliable distributed systems using Temporal. It focuses on critical design decisions like the separation of deterministic workflows from non-deterministic activities, implementing the Saga pattern for distributed transactions, and managing long-running stateful processes. Whether you are building complex e-commerce checkouts or infrastructure automation, this skill ensures your orchestration logic is robust, scalable, and recoverable from failures.

Características Principales

Deterministic state management and workflow versioning
Resilience patterns including exponential backoff and heartbeating
Parallel execution models like Fan-Out/Fan-In and Entity Workflows
Distributed transaction management via the Saga pattern
Temporal architecture patterns (Workflow vs. Activity separation)
89 GitHub stars

Casos de Uso

Designing e-commerce order fulfillment systems with automated compensation logic
Orchestrating multi-service infrastructure provisioning and CI/CD pipelines
Managing long-lived entity lifecycles such as account management or inventory tracking

Acerca de

Características Principales

Deterministic state management and workflow versioning
Resilience patterns including exponential backoff and heartbeating
Parallel execution models like Fan-Out/Fan-In and Entity Workflows
Distributed transaction management via the Saga pattern
Temporal architecture patterns (Workflow vs. Activity separation)
89 GitHub stars

Casos de Uso

Designing e-commerce order fulfillment systems with automated compensation logic
Orchestrating multi-service infrastructure provisioning and CI/CD pipelines
Managing long-lived entity lifecycles such as account management or inventory tracking