Why is determinism required in workflows?

Temporal preserves state by replaying event history; if the workflow code isn't deterministic, the replay could result in a different execution path, causing failure.

What is the core rule of Temporal workflow design?

The fundamental rule is that Workflows must be deterministic (orchestration logic) while Activities handle all non-deterministic external interactions like API calls or database writes.

How does this skill handle distributed transactions?

It utilizes the Saga pattern with compensation logic, ensuring that if a multi-step process fails, all previous successful steps are rolled back in reverse order.

When should I use an Entity Workflow?

Use an Entity Workflow when you need a long-lived process representing a single instance, like a shopping cart or bank account, that needs to maintain state over time.

Workflow Orchestration Patterns

Name: Workflow Orchestration Patterns
Author: HermeticOrmus

byHermeticOrmus

API開発

Designs resilient, distributed workflows using Temporal patterns to ensure reliability in complex microservice architectures.

概要

This skill provides specialized guidance for architecting durable distributed systems using Temporal. It enables developers to master the critical separation between deterministic orchestration logic (Workflows) and non-deterministic side effects (Activities). By implementing patterns like Sagas for distributed transactions, Entity Workflows for state management, and sophisticated retry policies, this skill helps ensure that long-running business processes remain consistent and recoverable even in the face of infrastructure failures.

主な機能

Saga pattern implementation for distributed transaction rollbacks
Entity workflow patterns for long-lived actor models
Resilience strategies including exponential backoffs and heartbeats
Deterministic state management and constraint validation
Temporal workflow vs. activity architectural separation
0 GitHub stars

ユースケース

Managing human-in-the-loop approval processes that persist for days or weeks
Automating complex infrastructure provisioning and CI/CD pipelines
Building multi-step e-commerce fulfillment systems with automated rollbacks

概要

主な機能

Saga pattern implementation for distributed transaction rollbacks
Entity workflow patterns for long-lived actor models
Resilience strategies including exponential backoffs and heartbeats
Deterministic state management and constraint validation
Temporal workflow vs. activity architectural separation
0 GitHub stars

ユースケース

Managing human-in-the-loop approval processes that persist for days or weeks
Automating complex infrastructure provisioning and CI/CD pipelines
Building multi-step e-commerce fulfillment systems with automated rollbacks