Announcing a new operation: Workflow Update

This post announces the General Availability of Workflow Updates, a new feature that allows clients to send messages to Workflows, wait for their completion, and receive a result or error. It details the technical differences between Updates, Signals, and Queries, highlighting how Updates enable lower-latency use cases and more efficient communication patterns. The post explains the internal mechanism of Updates, including how they defer writing to history until after delivery to the Workflow, and introduces three design patterns for using Updates: mutating local Workflow state, executing Activities or Child Workflows, and waiting for the Workflow to reach a certain state. Code examples in Java, Python, and Go are provided, along with links to documentation and samples.