workflow-orchestration-patterns

You model saga transactions as durable Temporal workflows that execute sequential steps and trigger rollback compensating actions automatically on failure. This ensures reliable distributed transactions across microservices.

Temporal enforces workflow determinism by requiring code to avoid non-deterministic calls, preserving state automatically, and combining idempotency patterns to safely retry failed operations without duplicate side effects in long-running processes.

The best way to coordinate parallel fan-out fan-in tasks is using Temporal workflows to execute concurrent activities across microservices and aggregate their results. This pattern handles parallel task execution reliably with automatic state preservation.

Async callbacks for human approval are handled by durable Temporal workflows that pause execution and wait for external events. The workflow resumes automatically once the callback signal is received, ensuring robust long-running process coordination.

Yes, you need prior Temporal knowledge and a configured Temporal environment to design entity-oriented workflows. This Skill models long-lived domain entities but requires understanding of determinism, idempotency, and Temporal setup.

You should avoid durable workflows for simple synchronous microservices orchestration where state preservation and compensation patterns add unnecessary overhead. Temporal workflows are best suited for complex, long-running processes requiring robust retries.