Workflows & orchestration · AWS vs Google Cloud
Lambda durable functions vs Workflows
Lambda durable functions have no direct counterpart.
Workflows provides durable, managed execution, but the steps are written in its YAML/JSON syntax rather than in a general-purpose language.
Side-by-side comparison
| Aspect | Amazon Web Services | Google Cloud |
|---|---|---|
| Service | Lambda durable functions | Workflows |
| Lifecycle | Generally available | Generally available |
| What it is | Multi-step workflows written as code (Durable Execution SDK) that checkpoint progress, replay after failures, and wait without compute charges. Runs up to one year. | Fully managed orchestration that runs steps written in YAML or JSON, calling Google Cloud services and HTTP APIs, billed per step executed. |
| Pricing model | Standard Lambda request and duration charges for active steps, plus durable-execution charges (see the Lambda pricing page). Waits don't incur compute charges. | Billed per workflow step executed. |
| Docs | Lambda durable functions docs | Workflows docs |
| Pricing page | Lambda durable functions pricing | Workflows pricing |
Key differences
- For code-first durable execution, teams run open-source engines such as Temporal on GKE.
Pricing summary
Pricing models only. No prices are quoted because they change by region and over time.
- AWS
- Standard Lambda request and duration charges for active steps, plus durable-execution charges (see the Lambda pricing page). Waits don't incur compute charges. Lambda durable functions pricing →
- GCP
- Billed per workflow step executed. Workflows pricing →
And on Azure?
Direct match Azure's equivalent is Durable Functions & Durable Task Scheduler. AWS vs Azure comparison →
FAQ
What is the Google Cloud equivalent of Lambda durable functions?
Lambda durable functions have no direct counterpart. Workflows provides durable, managed execution, but the steps are written in its YAML/JSON syntax rather than in a general-purpose language.
How does pricing compare between Lambda durable functions and Workflows?
AWS: Standard Lambda request and duration charges for active steps, plus durable-execution charges (see the Lambda pricing page). Waits don't incur compute charges. Google Cloud: Billed per workflow step executed. Check the official pricing pages for current rates.
What is the Azure equivalent?
Durable Functions & Durable Task Scheduler (direct match). Lambda durable functions map to Azure Durable Functions (with the Durable Task Scheduler backend).