-
Notifications
You must be signed in to change notification settings - Fork 1k
New Serverless pattern - lambda-durable-function-chaining-sam #2928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
New Serverless pattern - lambda-durable-function-chaining-sam #2928
Conversation
| FunctionName: durable-orchestrator | ||
| CodeUri: src/orchestrator/ | ||
| Handler: app.lambda_handler | ||
| Timeout: 900 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really
Co-authored-by: Ben <9841563+bfreiberg@users.noreply.github.com>
bfreiberg
left a comment
There was a problem hiding this 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
Co-authored-by: Ben <9841563+bfreiberg@users.noreply.github.com>
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.