Workflow Orchestration Patterns FAQs

Question 1

What is an Entity Workflow?

Accepted Answer

An Entity Workflow is a long-lived execution representing a specific instance, like a shopping cart or bank account, that persists state over time and responds to external signals.

Question 2

When should I avoid using Temporal for orchestration?

Accepted Answer

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

Question 3

How does the Saga pattern work in workflow orchestration?

Accepted Answer

The Saga pattern manages distributed transactions by registering a compensation action for every step performed; if a failure occurs, it executes the compensations in reverse order to roll back state.

Question 4

What is the core rule for separating Workflows and Activities?

Accepted Answer

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

Question 5

Why can't I use random numbers or system time inside a Workflow?

Accepted Answer

Temporal uses event replaying to recover state. Non-deterministic code like random() or datetime.now() would cause the replay to diverge from history, leading to workflow failure.

Workflow Orchestration Patterns

주요 기능

사용 사례

Workflow Orchestration Patterns

주요 기능

사용 사례