✳flâneur — a map of the web's best reading

Announcing a new operation: Workflow Update | Temporal

temporal.io · 2,008 words · saved by 1 readers

We’re excited to announce that Workflow Update is now Generally Available. This is a major new feature: in this blog post we’re going to look into why it’s important, see some examples of what it looks like to use it, and learn about design patterns when using Update in applications. Fundamentally, Update is about sending a message to a Workflow, waiting until the message handling is complete, and receiving a result or error in response. The Update handler in your Workflow code can do anything that normal Workflow code can do. That’s an extremely useful operation when building applications, but the existing messages, Query and Signal, did not provide it on their own. Let’s recap why that is: Since getting a result back after your Workflow has done some async work is such a common need, there were workarounds — for example sending a Signal and then polling repeatedly with a Query, or using an Activity to get the result back to your client code by some other means — but these feel very m

We’re excited to announce that Workflow Update is now Generally Available. This is a major new feature: in this blog post we’re going to look into why it’s important, see some examples of what it looks like to use it, and learn about design patterns when using Update in applications. Introducing Workflow Update # Fundamentally, Update is about sending a message to a Workflow, waiting until the message handling is complete, and receiving a result or error in response. The Update handler in your Workflow code can do anything that normal Workflow code can do. That’s an extremely useful operation

Explore this link on the map →

related reading