When should I avoid using workflow orchestration?

Avoid heavy orchestration for simple CRUD operations, stateless request/response APIs, or high-volume real-time data streaming where Kafka or simple event processors are more efficient.

Why is determinism required for workflows?

Temporal recovers workflow state by replaying event history. If the code is non-deterministic (e.g., uses random numbers or direct system time), the replay will produce different results than the original execution, leading to failure.

How does the Saga pattern work in this context?

The Saga pattern implements distributed transactions by registering a compensation action (rollback) before executing each step. If a failure occurs, the workflow executes the compensations in reverse order (LIFO).

What is the core rule for separating Workflows and Activities?

Workflows should contain only orchestration and decision logic and must be deterministic. Activities handle all external interactions like API calls, database writes, and network requests.

Workflow Orchestration Patterns

Name: Workflow Orchestration Patterns
Author: Activer007

byActiver007

Infraestructura en la Nube

Architects resilient distributed systems using Temporal patterns for durable workflows and fault-tolerant microservice orchestration.

Acerca de

This skill provides expert guidance on designing complex distributed systems using the Temporal orchestration model. It helps developers master the critical distinction between deterministic orchestration logic (Workflows) and non-deterministic external interactions (Activities). By implementing proven patterns like Sagas for distributed transactions, entity-based actor models, and fan-out/fan-in parallel execution, users can build reliable, long-running processes that automatically handle failures and state persistence. Whether you are building payment pipelines, infrastructure automation, or complex business logic, this skill ensures your architecture remains scalable, testable, and robust.

Características Principales

Resilience patterns including exponential backoff and activity heartbeats
0 GitHub stars
Scaling strategies for parallel task execution and child workflows
Saga pattern implementation for distributed transaction rollbacks
Determinism constraint management and state recovery logic
Temporal-based workflow vs. activity design separation

Casos de Uso

Managing complex entity lifecycles such as user account state or inventory tracking
Orchestrating long-running infrastructure provisioning and CI/CD pipelines
Building multi-step e-commerce fulfillment systems with rollback capabilities

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add activer007/ordinary-claude-skills workflow-orchestration-patterns

For use in Claude.ai and ChatGPT

Download Skill

GitHub