-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(clusters): convert clusters to new workflow system
- Loading branch information
1 parent
64b4054
commit 834ff6a
Showing
227 changed files
with
2,141 additions
and
2,373 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Signals | ||
|
||
## Tagged signals | ||
|
||
Tagged signals are consumed on a first-come-first-serve basis because a single signal being consumed by more | ||
than one workflow is not a supported design pattern. To work around this, consume the signal by a workflow | ||
then publish multiple signals from that workflow. | ||
|
||
# Choosing Between Signals and Messages | ||
|
||
> **Note**: non-workflow ecosystem is API layer, standalone, operations, old workers | ||
## Signal | ||
|
||
- Sending data from the non-workflow ecosystem to the workflow ecosystem | ||
- Sending data from the workflow ecosystem to somewhere else in the workflow ecosystem | ||
|
||
## Message | ||
|
||
- Sending data from the workflow ecosystem to the non-workflow ecosystem | ||
|
||
## Both Signals and Messages | ||
|
||
Sometimes you may need to listen for a particular event in the workflow system and the non-workflow ecosystem. | ||
In this case you can publish both a signal and a message (you can derive `signal` and `message` on the same | ||
struct to make this easier). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.