Skip to content
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.

Sign up for GitHub

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

EDU-3748: Tweak signal vs update text #3277

Merged
merged 3 commits into from
Jan 22, 2025
Merged

EDU-3748: Tweak signal vs update text #3277

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
34586ab
Tweak signal vs update text
dandavison Jan 7, 2025
cfb1b64
Tweak
dandavison Jan 8, 2025
56a009e
Merge branch 'main' into message-passing-tweak
fairlydurable Jan 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/encyclopedia/application-message-passing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Unlike Signals, Updates must be synchronous. That is, they must wait for the Wor
Use Signals instead of Updates when:

- The Workflow's clients want to quickly move on after sending an asynchronous message.
- The clients care more about the latency of sending the message than they do about the latency of the end-to-end operation.
- The clients are willing to "fire and forget": they don't want a result or exception from the message.
- The clients don't want to rely on the Worker being available.

Use Updates instead of Signals when:
Expand Down
Loading