Lambda Durable Functions(docs.aws.amazon.com)
docs.aws.amazon.com
Lambda Durable Functions
https://docs.aws.amazon.com/lambda/latest/dg/durable-functions.html
9 comments
This is really exciting. Step functions were a big improvement over SWF and the Flow framework, but declarative workflow authoring sucks from a type-safety standpoint. Workflows-as-code is the way to go, and that was missing from AWS. Can't wait to build on top of this.
AWS announced Lambda durable functions today in a blog post titled "Build multi-step applications and AI workflows with AWS Lambda durable functions" [0]
[0] https://aws.amazon.com/blogs/aws/build-multi-step-applicatio...
[0] https://aws.amazon.com/blogs/aws/build-multi-step-applicatio...
Is this just DBOS under the hood?
"Durable functions are available for Node.js and Python runtimes."
If you're only working with those languages, you can use durable functions. Otherwise, you're SOL.
If you're only working with those languages, you can use durable functions. Otherwise, you're SOL.
This post seems to be published in a hurry. Under "How it works" section a bunch of duplication, and I think they should make the blog post exactly once :) Excerpt from the blog post:
> During replay, your code runs from the beginning but skips over completed checkpoints, using stored results instead of re-executing completed operations. This replay mechanism ensures consistency while enabling long-running executions. > > ... During replay, your code runs from the beginning but skips over completed checkpoints, using stored results instead of re-executing completed operations. This replay mechanism ensures consistency while enabling long-running executions.
> During replay, your code runs from the beginning but skips over completed checkpoints, using stored results instead of re-executing completed operations. This replay mechanism ensures consistency while enabling long-running executions. > > ... During replay, your code runs from the beginning but skips over completed checkpoints, using stored results instead of re-executing completed operations. This replay mechanism ensures consistency while enabling long-running executions.
The distributed state associated with workflow systems like this makes observability and code upgrades a challenge compared to just having an application orchestrating workflows with progress persisted in a shared database. But if they solve those problems this would be really nice, as I've seen a ton of home-grown systems re-write checkpointing, retries, etc. and usually get it wrong.
This basically is just a an application with steps that are checkpointed when they progress in a shared database (that's abstracted away from you).
It's considerably simpler, less magical and cheaper than the equivalent Step Function-style implementation would be.
It's considerably simpler, less magical and cheaper than the equivalent Step Function-style implementation would be.
Sounds like a step in the right direction. I would like to see an all-up dashboard of everything in the shared state, and good control over upgrades (maybe a mode where in-progress functions can complete on version 1, even if new functions are getting kicked off on version 2, etc.)
But if you did that, you'd also have to implement it all yourself. This is a relatively simple checkpointing workflow orchestrator across standard Lambda functions, but with some really nice touch surfaces in the Lambda API itself.
What's only a footnote in the announcement is that this is only us-east-2 (Ohio) and TypeScript/JS + Python at the moment. Basically a public preview release. I look forward to seeing where they take this.