Temporal Workflow message passing - Signals, Queries, & Updates | Temporal Platform Documentation
docs.temporal.io · 448 words · saved by 1 readers
Signals, Queries, and Updates facilitate interactions with Workflow Executions.
On this page Workflows can be thought of as stateful web services that can receive messages. The Workflow can have powerful message handlers akin to endpoints that react to the incoming messages in combination with the current state of the Workflow. Temporal supports three types of messages: Signals, Queries, and Updates: Queries are read requests. They can read the current state of the Workflow but cannot block in doing so. Signals are asynchronous write requests. They cause changes in the running Workflow, but you cannot await any response or error. Updates are synchronous, tracked write req
related reading
- Workflow message passing - Java SDK | Temporal Platform Documentationdocs.temporal.io
- Announcing a new operation: Workflow Update | Temporaltemporal.io
- Temporal Primer - Building Long-Running Systemsarpitbhayani.me
- Temporal Workflow | Temporal Platform Documentationdocs.temporal.io
- What is a Temporal Activity? | Temporal Platform Documentationdocs.temporal.io
- Reading 18: Message-Passing and Networkingweb.mit.edu
- Durable Execution Solutionstemporal.io
- What is a Temporal Activity? | Temporal Platform Documentationdocs.temporal.io
- Message Passing - Documentationaeron.io
- Durable Execution Solutions | Temporaltemporal.io
- temporal/docs/architecture/history-service.md at main · temporalio/temporal · GitHubgithub.com
- Reading 15: Promisesweb.mit.edu