Question 1

What’s the difference between Workflows and serverless functions (like AWS Lambda)?

Accepted Answer

A serverless function runs a single piece of code for one step (e.g., resize an image). A workflow coordinates many steps—often multiple functions and services—into an end-to-end process with ordering, branching, retries, timeouts, and error handling.

Question 2

When should I use Workflows?

Accepted Answer

Use workflows when you have a multi-step process that needs coordination and reliability—such as approvals, data pipelines, file processing, order fulfillment, or provisioning infrastructure. Workflows are especially useful when steps can fail and you need retries, compensation steps (undo actions), or clear visibility into where a process is stuck.

Question 3

How much do Workflows cost?

Accepted Answer

Costs usually depend on how many workflow executions you run, how many steps/transitions occur, and how long executions run. You may also pay for connected services (functions, containers, databases, API calls). Pricing varies by provider and features (e.g., standard vs. express/short-duration modes), so estimate using expected executions per month, average steps per execution, and any long-running waits.

Workflows

Definition

Real-World Example

Related Terms

Cloud Provider Equivalencies

Explore More Cloud Computing Terms