What are determinism constraints in Temporal?

Workflows must be deterministic because they are replayed to restore state. You cannot use random numbers, system time, or direct network calls within the workflow logic itself.

What is the difference between a Workflow and an Activity?

Workflows contain orchestration logic and must be deterministic to ensure state recovery, while Activities handle external interactions like API calls and can be non-deterministic.

How does this skill help with distributed transactions?

It implements the Saga Pattern, which allows you to register compensation actions for every step, ensuring the system can rollback changes in reverse order upon failure.

When should I avoid using workflow orchestration?

Orchestration is overkill for simple CRUD operations, stateless request/response APIs, or high-volume real-time data streaming where tools like Kafka are more appropriate.

Workflow Orchestration Patterns

Name: Workflow Orchestration Patterns
Author: Microck

byMicrock

•

クラウドインフラストラクチャ

Designs and implements resilient, durable workflows for distributed systems using Temporal architecture principles.

概要

This skill provides comprehensive guidance on building reliable distributed systems using Temporal's orchestration patterns. It assists developers in distinguishing between deterministic workflows and side-effect-heavy activities, implementing robust error-handling strategies like the Saga pattern, and managing state across long-running processes. Whether you are building complex e-commerce checkouts, CI/CD pipelines, or human-in-the-loop systems, this skill ensures your architecture remains fault-tolerant, scalable, and capable of automatic recovery from infrastructure failures.

主な機能

Implements the Saga pattern for distributed transaction rollbacks
Enforces determinism constraints for reliable workflow replay
Configures intelligent retry policies and activity heartbeats
81 GitHub stars
Designs entity workflows for long-lived state management
Optimizes separation between orchestration logic and external activities

ユースケース

Automating complex infrastructure provisioning and CI/CD pipelines
Building multi-step payment and booking systems with compensation logic
Managing long-running human-approval processes and lifecycle events

概要

主な機能

Implements the Saga pattern for distributed transaction rollbacks
Enforces determinism constraints for reliable workflow replay
Configures intelligent retry policies and activity heartbeats
81 GitHub stars
Designs entity workflows for long-lived state management
Optimizes separation between orchestration logic and external activities

ユースケース

Automating complex infrastructure provisioning and CI/CD pipelines
Building multi-step payment and booking systems with compensation logic
Managing long-running human-approval processes and lifecycle events