⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@sbbhimji
Copy link

@sbbhimji sbbhimji commented Feb 6, 2026

Issue #, if available:
#2929

Description of changes:
This pattern demonstrates the function chaining workflow pattern using AWS Lambda durable functions. A durable orchestrator function sequentially invokes three Lambda functions using context.invoke(), where each invocation automatically creates a checkpoint. The key benefit is fault tolerance: if the orchestrator fails mid-execution, it replays from the beginning but skips completed steps by loading results from checkpoints, ensuring no work is re-executed. This
pattern showcases how developers can build resilient, multi-step workflows directly in Python code without managing external state infrastructure, leveraging the new Lambda durable functions capability and the aws-durable-execution-sdk-python SDK. This also leverages SAM for the deployment of the durable function.

FunctionName: durable-orchestrator
CodeUri: src/orchestrator/
Handler: app.lambda_handler
Timeout: 900
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is such a high timeout necessary?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really

Copy link
Contributor

@bfreiberg bfreiberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, one more round and I think we are good to go

@bfreiberg bfreiberg added the durable functions Pattern for AWS Lambda durable functions label Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

durable functions Pattern for AWS Lambda durable functions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants