workflow-orchestration-patterns

Design durable distributed workflows with Temporal, separating orchestration logic from external interactions. Master workflow orchestration architecture with Temporal, covering fundamental design decisions, resilience patterns, and best practices for building reliable distributed systems. The Fundamental Rule (Source: temporal.io/blog/workflow-engine-principles): Characteristics: Example workflow tasks: Characteristics: Example activity tasks: Purpose : Implement distributed transactions with rollback capability Pattern (Source: temporal.io/blog/compensating-actions-part-of-a-complete-breakfast-with-sagas): Example: Payment Workflow Critical Requirements: Purpose : Long-lived workflow representing single entity instance Pattern (Source: docs.temporal.io/evaluate/use-cases-design-patterns): Example Use Cases: Benefits: Purpose : Execute multiple tasks in parallel, aggregate results Pattern: Scaling Rule (Source: temporal.io/blog/workflow-engine-principles): Purpose : Wait for external event or human approval Pattern: Use Cases: How Temporal Works (Source: docs.temporal.io/workflows): Workflows Execute as State Machines : Prohibited in Workflows (Source: docs.temporal.io/workflows): Allowed in Workflows : Challenge : Changing workflow code while old executions still running Solutions : Default Behavior : Temporal retries activities forever Configure Retry : Non-Retryable Errors...